Skip to content

feat: add action.yml composite wrapper + supporting workflows#10

Merged
lesnik512 merged 11 commits into
mainfrom
feat/action-yml-composite-wrapper
Jun 8, 2026
Merged

feat: add action.yml composite wrapper + supporting workflows#10
lesnik512 merged 11 commits into
mainfrom
feat/action-yml-composite-wrapper

Conversation

@lesnik512

@lesnik512 lesnik512 commented Jun 8, 2026

Copy link
Copy Markdown
Member

Summary

  • Add action.yml so users can write uses: modern-python/semvertag@v0 instead of pasting the 11-line install-and-run block.
  • Add .github/workflows/tag-major.yml to maintain the floating v0 major tag on each non-prerelease release.
  • Migrate the dogfood workflow to consume uses: ./ and add a PR-time action-smoke CI job.
  • Rewrite README + docs/providers/github.md around the action; preserve the pure-CLI recipe as the "Without the composite action" fallback.
  • Add planning/releases/0.4.0.md runbook including the manual Marketplace publication procedure.

Spec and plan

  • Spec: `planning/specs/2026-06-08-action-yml-composite-wrapper-design.md`
  • Plan: `planning/plans/2026-06-08-action-yml-composite-wrapper.md`

Test plan

  • CI green on this PR (lint, pytest matrix, action-smoke).
  • After merge: dogfood workflow on main creates a tag (this PR is on a `feat/` branch, so branch-prefix maps it to a minor bump → v0.4.0).
  • After v0.4.0 release: bootstrap the floating `v0` tag per the runbook.
  • After Marketplace publish: smoke-test `uses: modern-python/semvertag@v0` in a sandbox repo.

lesnik512 and others added 9 commits June 8, 2026 22:48
Brainstorm output for the composite GitHub Action that lets users
replace the 11-line install-and-run block with `uses:
modern-python/semvertag@v0`. Scope: action.yml + tag-major.yml
floating-tag workflow + dogfood/CI/docs migration + v0.4.0 release
runbook including the manual Marketplace publication procedure.
Bite-sized 8-task plan derived from the spec. Spec revision: CLI floor
in action.yml is `>=0.3.1,<1` (not `>=0.4,<1`) so the PR landing this
work satisfies its own action-smoke CI from PyPI today; the floor
only bumps when a future release breaks CLI contract.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@lesnik512 lesnik512 force-pushed the feat/action-yml-composite-wrapper branch from 33accd9 to e18e7b8 Compare June 8, 2026 20:39
lesnik512 added 2 commits June 8, 2026 23:46
Spec/plan picked @v8 as the "current latest" major, but astral only
publishes floating major tags up to @v7 — specific v8.0.0/v8.1.0/v8.2.0
releases exist, but no `v8` ref. `@v8` resolved to nothing in CI
(initially fixed via @V3 to match ci.yml; this commit upgrades to @v7
to stay closest to upstream's actual current).

Spec, plan, and runbook updated to match.
The CLI emits internal status strings (`no_tags`, `already_tagged`,
`no_merge_commit`, `no_conforming_commit`, `created`) but the action's
documented enum was `created | no-bump | error` — consumers writing
`if: outputs.status == 'no-bump'` would silently never match.

Normalize inside the composite via a bash `case`: `created` stays
`created`; everything else collapses to `no-bump`. `set -euo pipefail`
already exits on CLI errors, so no `error` value is ever written —
documentation tightened to reflect that.

Spec / plan / provider docs updated to match.
@lesnik512 lesnik512 self-assigned this Jun 8, 2026
@lesnik512 lesnik512 merged commit 4a09b6f into main Jun 8, 2026
6 checks passed
@lesnik512 lesnik512 deleted the feat/action-yml-composite-wrapper branch June 8, 2026 21:00
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