Skip to content

chore: adjust versions after the 3.10.0 release - #2950

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
post-release-3.10.0
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
post-release-3.10.0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

3.10.0 is drafted, so main goes back to a development version.

  • ops and ops-tracing go to 3.11.0.dev0, and ops-scenario follows it.
  • The tool-versions table is left alone: it records releases, and this is not one.

This is safe to merge before the draft release is published: the draft is pinned to the commit that was reviewed, not to the branch.

The version here is a placeholder that stops the tree claiming to be 3.10.0. Nothing counts from it - the next release is counted from the last tag on the branch - so it does not matter if the next release turns out to be a different one.

@dwilding
dwilding requested a review from tromai November 20, 2026 06:02
@dwilding

Copy link
Copy Markdown
Contributor

The example charm CI is blocked by #2951

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants