Skip to content

[releng] Bump version to 2026.9.4 - #2562

Closed
pcdavid wants to merge 2 commits into
mch/exp/2026.9.4from
pcd/rel/bump-2026.9.4
Closed

pcdavid wants to merge 2 commits into
mch/exp/2026.9.4from
pcd/rel/bump-2026.9.4

Conversation

@pcdavid

@pcdavid pcdavid commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Signed-off-by: Pierre-Charles David pierre-charles.david@obeo.fr

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@pcdavid
pcdavid marked this pull request as draft October 23, 2026 12:22
@pcdavid

pcdavid commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

Draft for now, will be rebased on top of the upcoming PR which switches to Sirius Web 2026.9.4 when it's ready.

mcharfadi and others added 2 commits October 23, 2026 14:24
Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
Signed-off-by: Pierre-Charles David <pierre-charles.david@obeo.fr>
@pcdavid
pcdavid force-pushed the pcd/rel/bump-2026.9.4 branch from 5b4b6ff to b94aedc Compare October 23, 2026 12:28
@pcdavid
pcdavid changed the base branch from main to mch/exp/2026.9.4 October 23, 2026 12:28
@pcdavid
pcdavid marked this pull request as ready for review October 23, 2026 12:29
@pcdavid pcdavid added this to the 2026.11.0 milestone Oct 23, 2026
@pcdavid
pcdavid force-pushed the mch/exp/2026.9.4 branch 2 times, most recently from 08dbefa to 40c29cd Compare October 23, 2026 13:00
@pcdavid

pcdavid commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

Added this commit directly into #2563.

@pcdavid pcdavid closed this Oct 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants