fix(release): drop the moving current tag; consumers pin release tags - #11
Merged
Conversation
Reverts the `current` half of #10 (the gpt-5.6-terra switch stays). release.yml no longer force-moves a `current` tag; README documents pinning a dated release tag (currently 1.32.20260826) and bumping deliberately. The `current` tag itself is deleted from origin once every consumer PR references 1.32.20260826. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3 tasks
Contributor
Author
|
Deleted the |
absorbb
added a commit
to jitsucom/jitsu
that referenced
this pull request
Aug 26, 2026
…826 (#1485) ## Summary Follow-up to #1482 (merged before this could be folded in). - `security-fix.yml`: `gpt-5.3-codex` → `gpt-5.6-terra` (`effort: high` unchanged), matching the ai-review model switch released as github-workflows `1.32.20260826` (jitsucom/github-workflows#10). Terra is in the pinned codex CLI 0.149.0 preset list; 5.3-codex no longer is. - `ai-review.yml`: bump the pinned `jitsucom/github-workflows` release from `1.30.20260821` to `1.32.20260826`. (An earlier revision of this PR used a floating `current` tag; that approach is rolled back in jitsucom/github-workflows#11 and the tag is removed.) ## Test plan - [x] YAML parses; diff reviewed - [ ] The AI Review check on this PR runs on Terra (job summary shows `Model: gpt-5.6-terra`) - [ ] Next `security-fix` run (Monday 08:00 UTC, or `workflow_dispatch` with `dry_run: true`) completes the Codex step on Terra 🤖 Generated with [Claude Code](https://claude.com/claude-code)
current tag; consumers pin release tagscurrent tag; publish immutable releases
3 tasks
current tag; publish immutable releasescurrent tag; consumers pin release tags
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rolls back the moving-
current-tag half of #10; thegpt-5.6-terraswitch stays (it shipped as1.32.20260826).release.yml: restored to its pre-feat(ai-review): switch to gpt-5.6-terra; add movingcurrenttag #10 content — no more force-moving acurrenttag on each release.README.md: usage example pins@1.32.20260826; the "Versioning" section says consumers pin a dated release tag and bump deliberately, no floating tag.currenttag was deleted from origin (it pointed atd3c646e==1.32.20260826); nothing on any default branch referenced it.Consumer PRs re-pointed from
@currentto@1.32.20260826: jitsucom/jitsu#1485, jitsucom/ai-tooling#2, jitsucom/jitsu-cloud-billing#37, jitsucom/jitsu-cloud-infra#92, jitsucom/source-connectors#6, jitsucom/websites#65.Making release tags immutable (repo setting +
gh release createinrelease.yml) is the follow-up #12.Test plan
release.ymlbyte-identical toe3144b9:.github/workflows/release.yml;ai-review.ymluntouched1.34.20260826only;git ls-remote origin currentis empty🤖 Generated with Claude Code