Skip to content

commit release versions after release#38

Merged
tarik02 merged 1 commit into
mainfrom
fix-release-package-version-build
Jun 19, 2026
Merged

commit release versions after release#38
tarik02 merged 1 commit into
mainfrom
fix-release-package-version-build

Conversation

@tarik02

@tarik02 tarik02 commented Jun 19, 2026

Copy link
Copy Markdown
Owner

What Changed

  • Re-enable the release finalization job for the fork so successful releases commit the derived release version back to main.
  • Update fork notes to document that package manifests now track released versions after release.

Why

Runtime code reads version values from package manifests. Keeping the released version committed on main avoids drift without mutating package manifests inside the desktop artifact build.

Checklist

  • This PR is small and focused
  • I explained what changed and why
  • UI not changed

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XS labels Jun 19, 2026
@tarik02 tarik02 force-pushed the fix-release-package-version-build branch from 0ad2f0a to 3c7a961 Compare June 19, 2026 16:06
@tarik02 tarik02 changed the title align package versions during desktop builds commit release versions after release Jun 19, 2026
@tarik02 tarik02 merged commit d07feb5 into main Jun 19, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant