Skip to content

ci: backport release-type labeling from main to maintenance2026 - #147

Merged
so5 merged 1 commit into
RIKEN-RCCS:maintenance2026from
so5:backport/release-labeling-maintenance2026
Sep 22, 2026
Merged

so5 merged 1 commit into
RIKEN-RCCS:maintenance2026from
so5:backport/release-labeling-maintenance2026

Conversation

@so5

@so5 so5 commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

Backports the release-type labeling scheme introduced on main in #145 to maintenance2026's own copy of build_and_deploy.yml, so its next workflow_dispatch release shows correctly:

  • Title prefix 🔧 Maintenance ... (this branch's name always resolves to TYPE=maintenance)
  • Real (non-prerelease) release, never takes the "Latest" badge

The workflow_dispatch-only trigger is unchanged - this is a display/labeling-only change, not a trigger change.

Part of the branch-strategy/release-artifact cleanup started in #145.

🤖 Generated with Claude Code

https://claude.ai/code/session_01C3jKNM1qubomM8UTRdkEWu

…rategy work)

Bring maintenance2026's build_and_deploy.yml in line with main's release
labeling scheme (see RIKEN-RCCS#145): each release type gets a
distinct title prefix (release/maintenance/beta - unreachable "release"
and "beta" cases kept only for parity with main's copy, since this
branch's own name always resolves to TYPE=maintenance), and maintenance
releases are real (non-prerelease) releases that never take the "Latest"
badge - previously every non-master build was marked prerelease
regardless of type.

Also carries over SAFE_BRANCH_NAME (BRANCH_NAME with "/" stripped) for
consistency with main's copy, even though this branch's own name has no
slash to strip.

Trigger (workflow_dispatch only) is unchanged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C3jKNM1qubomM8UTRdkEWu
@so5
so5 merged commit 1763e56 into RIKEN-RCCS:maintenance2026 Sep 22, 2026
@so5
so5 deleted the backport/release-labeling-maintenance2026 branch September 22, 2026 15:20
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