Skip to content

chore(ci): migrate release workflow labels to linearis-bot app naming#169

Merged
iamfj merged 2 commits intonextfrom
chore/linearis-bot-workflow-migration-spec
Apr 23, 2026
Merged

chore(ci): migrate release workflow labels to linearis-bot app naming#169
iamfj merged 2 commits intonextfrom
chore/linearis-bot-workflow-migration-spec

Conversation

@iamfj
Copy link
Copy Markdown
Member

@iamfj iamfj commented Apr 23, 2026

Summary

  • rename GitHub Actions step labels in release workflows to explicitly reference linearis-bot app identity
  • update both sync and release-check workflows with text-only label changes
  • preserve workflow behavior (no id/env/secret/script/trigger/permission changes)

Test Plan

  • rg label checks for both workflow files (new labels present, old labels removed)
  • npm run check:ci
  • npm test

@iamfj iamfj changed the base branch from main to next April 23, 2026 09:35
@iamfj iamfj force-pushed the chore/linearis-bot-workflow-migration-spec branch from 9b3242c to 953b41c Compare April 23, 2026 09:36
@iamfj iamfj force-pushed the chore/linearis-bot-workflow-migration-spec branch from 953b41c to 35f94c6 Compare April 23, 2026 09:37
@iamfj iamfj merged commit 318e08d into next Apr 23, 2026
10 checks passed
@iamfj iamfj deleted the chore/linearis-bot-workflow-migration-spec branch April 23, 2026 09:39
@chatgpt-codex-connector
Copy link
Copy Markdown

💡 Codex Review

context.nextRelease.version = nextVersion;

P1 Badge Update gitTag after forcing a CalVer version

This hook overrides context.nextRelease.version but leaves context.nextRelease.gitTag/name untouched, and semantic-release computes those fields before verifyRelease. When your CalVer output diverges from the default semantic bump (for example at UTC month rollover), the run can publish artifacts/changelog with one version while creating/pushing a different tag, which breaks release consistency and can cause later release failures due to unexpected existing tags.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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