fix: run release-please on this repo - #5
Merged
Merged
Conversation
This repo publishes release-please.yaml for other repos to call, but nothing called it here, so its own releases were never cut and v0.4.0 never appeared after #4 merged. Add a caller that triggers on push to main. Use the self-repository form so the call resolves to the running commit rather than a pinned masterpointio/actions ref that would need bumping every release. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
oycyc
approved these changes
Sep 21, 2026
gberenice
pushed a commit
that referenced
this pull request
Sep 21, 2026
🤖 I have created a release *beep* *boop* --- ## [0.4.0](v0.3.0...v0.4.0) (2026-09-21) ### Features * discover and test every module in tf-test workflow ([#4](#4)) ([5ca743a](5ca743a)) ### Bug Fixes * run release-please on this repo ([#5](#5)) ([fc531db](fc531db)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: masterpointbot[bot] <177651640+masterpointbot[bot]@users.noreply.github.com>
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.
Problem
release-please.yamlhere isworkflow_call-only — it exists for other repos to consume. Nothing in this repo ever called it, so release-please has never run and no release was cut when #4 merged.Consumers like
github-action-tf-testhave the caller half; this repo only had the callee half.Two consequences, both fixed:
self-release-please.yaml, triggering on push tomain.v0.1.0–v0.3.0existed only as lightweight git tags created by hand. Release-please reads the Releases API to find the last version, so it would have ignored those tags and restarted versioning at1.0.0. I backfilled releases for all three tags, withv0.3.0marked latest, so the next run proposesv0.4.0.Self-repository syntax
The call uses
$/rather than./:GitHub shipped this in July 2026. It resolves to the exact running commit with no checkout, and unlike
./it counts as pinning for policy enforcement — which matters for a repo whose whole purpose is publishing pinned workflows. zizmor'sself-repositoryaudit recommends it. The alternative, pinning tomasterpointio/actions@<sha>, would need a bump on every single release.Tradeoff worth flagging: actionlint 1.7.12 predates the syntax and rejects it, hence the scoped
trunk-ignore. Requires runner 2.336.0+, which GitHub-hosted runners satisfy. If the first run fails, swapping$/for./is a one-line fallback.Follow-up
This repo also runs no CI on its own PRs —
lint.yamlis likewiseworkflow_call-only and there's no.trunkconfig. Separate PR, so a first-time trunk run surfacing pre-existing findings doesn't block this release fix.Testing
actionlint,zizmor --persona=pedantic,yamllint, andprettierpass locally (borrowing a trunk config, since this repo has none).Made with Cursor