Skip to content

commit release versions after release #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tarik02 merged 1 commit into from
Jun 19, 2026
Merged

commit release versions after release #38

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -883,7 +883,7 @@ jobs:

finalize:
name: Finalize release
if: false # Disabled for the fork: avoid committing release-only version bumps back to main.
if: ${{ !failure() && !cancelled() && needs.preflight.result == 'success' && needs.release.result == 'success' }}
needs: [preflight, release]
runs-on: ubuntu-latest
timeout-minutes: 10
Expand Down
2 changes: 1 addition & 1 deletion FORK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This repository is a fork of `pingdotgg/t3code`. Keep this file focused on fork
- Fork workflows disable scheduled releases, relay jobs, hosted deploys, and fork-unsafe publish paths.
- Release build jobs skip relay client tracing config because the relay config job is disabled.
- Release builds publish updater metadata against the fork repository.
- Fork release versions are derived in the release workflow so package manifests stay close to upstream.
- Fork release versions are derived in the release workflow and committed back to main after release.
- macOS release signing is separate from Apple notarization.
- Self-signed macOS signing certificates are trusted during release builds.

Expand Down
Loading