Skip to content

ci: registration of v1.x working release branch - #2240

Merged
bosbaber merged 3 commits into
mainfrom
stephan/v1x-release-channel
Sep 16, 2026
Merged

bosbaber merged 3 commits into
mainfrom
stephan/v1x-release-channel

Conversation

@bosbaber

Copy link
Copy Markdown
Contributor

Context

Since we are about to embark on massive restructuring and API changes to the TestNet wallet application, we decided that we will make these changes against a v1.x development branch instead of main. This way normal maintenance can continue on main against v0.x as per usual.

Changes

This pull request updates the release process to support a new v1.x release branch alongside main, improves Docker image tagging logic, and upgrades Node.js and semantic-release dependencies. These changes enable parallel development of the next major version while maintaining stable releases from main.

@bosbaber
bosbaber requested a lite review from Copilot September 16, 2026 07:36
@bosbaber bosbaber self-assigned this Sep 16, 2026
@github-actions github-actions Bot added the type: ci Changes to CI workflows label Sep 16, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The v1.x branch behavior described in release.config.js isn’t made explicit in configuration (channel/prerelease intent), which risks relying on semantic-release defaults for a critical release-path change.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This PR updates the repository’s release/CI configuration to support parallel development and releasing from a new v1.x branch while keeping main as the stable v0.x production line. It adjusts semantic-release branch registration, updates the release workflow toolchain, and ensures :latest Docker tags remain tied to the production branch only.

Changes:

  • Register v1.x as an additional semantic-release branch alongside main (plus existing dynamic maintenance branches).
  • Update the “Create Release” workflow to allow releases from v1.x, upgrade Node.js and semantic-release tooling, and compute Docker tags so :latest is only published from main.
  • Enable E2E workflow triggering for PRs targeting v1.x.
File summaries
File Description
release.config.js Adds v1.x as a configured release branch alongside main and documents the intended multi-branch release behavior.
.github/workflows/release.yml Allows releases from v1.x, upgrades Node/semantic-release, and changes image tagging so :latest only follows main.
.github/workflows/e2e.yml Expands PR branch triggers to include v1.x so E2E runs for PRs targeting that branch.
Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread release.config.js
@bosbaber
bosbaber force-pushed the stephan/v1x-release-channel branch from fbeedea to 3c41a7f Compare September 16, 2026 07:46
@bosbaber
bosbaber marked this pull request as ready for review September 16, 2026 07:54
dragosp1011
dragosp1011 previously approved these changes Sep 16, 2026
@bosbaber
bosbaber merged commit 23834d2 into main Sep 16, 2026
14 checks passed
@bosbaber
bosbaber deleted the stephan/v1x-release-channel branch September 16, 2026 08:24
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.10.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@github-actions

github-actions Bot commented Oct 1, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 0.10.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants