Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: backport release freeze workflow to 2.27#20132

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.

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

Already on GitHub?Sign in to your account

Merged
deansheather merged 1 commit intorelease/2.27fromdean/release-freeze-backport
Oct 2, 2025

Conversation

deansheather
Copy link
Member

@deansheatherdeansheather commentedOct 2, 2025
edited
Loading

Relates tohttps://github.com/coder/dogfood/pull/189
Relates tocoder/internal#1021

  • Adds new scriptscripts/should_deploy.sh which implements the algorithm in the linked issue
  • Changes theci.yaml workflow to run on release branches
  • Moves the deployment steps out ofci.yaml into a new workflowdeploy.yaml for concurrency limiting purposes
  • Changes the behavior of image tag pushing slightly:
    • Versioned tags will no longer have amain- prefix
    • main branch will still push themain andlatest tags
    • release/x.y branches will now pushrelease-x.y tags
  • The deploy job will exit early ifshould_deploy.sh returns false
  • The deploy job will now retag whatever image it's about to deploy asdogfood

(cherry picked from commite5c8c9b)

Relates tocoder/dogfood#189Closescoder/internal#1021- Adds new script `scripts/should_deploy.sh` which implements thealgorithm in the linked issue- Changes the `ci.yaml` workflow to run on release branches- Moves the deployment steps out of `ci.yaml` into a new workflow`deploy.yaml` for concurrency limiting purposes- Changes the behavior of image tag pushing slightly:    - Versioned tags will no longer have a `main-` prefix    - `main` branch will still push the `main` and `latest` tags    - `release/x.y` branches will now push `release-x.y` tags- The deploy job will exit early if `should_deploy.sh` returns false- The deploy job will now retag whatever image it's about to deploy as`dogfood`(cherry picked from commite5c8c9b)
@deansheatherdeansheather changed the titlechore: pin dogfood to release branch during release freeze (#20028)chore: backport release freeze workflow to 2.27Oct 2, 2025
@deansheatherdeansheather changed the base branch frommain torelease/2.27October 2, 2025 02:17
@deansheatherdeansheather marked this pull request as ready for reviewOctober 2, 2025 02:45
@deansheatherdeansheather merged commitc2414d5 intorelease/2.27Oct 2, 2025
41 of 43 checks passed
@deansheatherdeansheather deleted the dean/release-freeze-backport branchOctober 2, 2025 02:45
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsOct 2, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@ethanndicksonethanndicksonethanndickson approved these changes

Assignees

@deansheatherdeansheather

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Dogfood upcoming release during code freeze
2 participants
@deansheather@ethanndickson

[8]ページ先頭

©2009-2025 Movatter.jp