Skip to content

fix(release): drop the moving current tag; consumers pin release tags - #11

Merged
absorbb merged 1 commit into
mainfrom
fix/drop-current-tag
Aug 26, 2026
Merged

fix(release): drop the moving current tag; consumers pin release tags#11
absorbb merged 1 commit into
mainfrom
fix/drop-current-tag

Conversation

@absorbb

@absorbb absorbb commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Rolls back the moving-current-tag half of #10; the gpt-5.6-terra switch stays (it shipped as 1.32.20260826).

  • release.yml: restored to its pre-feat(ai-review): switch to gpt-5.6-terra; add moving current tag #10 content — no more force-moving a current tag 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.
  • The current tag was deleted from origin (it pointed at d3c646e == 1.32.20260826); nothing on any default branch referenced it.

Consumer PRs re-pointed from @current to @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 create in release.yml) is the follow-up #12.

Test plan

  • release.yml byte-identical to e3144b9:.github/workflows/release.yml; ai-review.yml untouched
  • After merge: release run created 1.34.20260826 only; git ls-remote origin current is empty

🤖 Generated with Claude Code

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>
@absorbb

absorbb commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

Deleted the current tag from origin (it pointed at d3c646e == 1.32.20260826). All six consumer PRs now pin @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.

@jitsu-code-review jitsu-code-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reviewed the release-tag workflow and the consumer documentation.

Finding:

  • Existing callers using the previously recommended @current reference will silently stop receiving releases because the remote tag remains but is no longer advanced.

Comment thread .github/workflows/release.yml
@absorbb
absorbb merged commit e0dbecd into main Aug 26, 2026
1 check passed
@absorbb
absorbb deleted the fix/drop-current-tag branch August 26, 2026 14:25
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)
@absorbb absorbb changed the title fix(release): drop the moving current tag; consumers pin release tags fix(release): drop the moving current tag; publish immutable releases Aug 26, 2026

@jitsu-code-review jitsu-code-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reviewed the release workflow and versioning documentation.

No new actionable findings. The existing resolved thread covers the migration impact of removing the floating current tag.

@absorbb absorbb changed the title fix(release): drop the moving current tag; publish immutable releases fix(release): drop the moving current tag; consumers pin release tags Aug 26, 2026

@jitsu-code-review jitsu-code-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Reviewed the release-tag change and the reusable-workflow documentation. I found no new actionable correctness, security, or user-visible regression issues. The existing resolved migration discussion was considered and is not repeated here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant