chore: bump baseline to v0.15.0, adopt release-please embedder policy - #129
Merged
Conversation
Baseline v0.14.0 added an optional "extra" embedder config for release-please conventions (chore: release title pattern, standard PR header/footer, release-please-action usage, and a semantic PR title check). Opt in via embedder.yml's new `extra` input, add the two missing release-please-config.json keys, and add pr.yml running amannn/action-semantic-pull-request to lint PR titles - all four baseline workflow pins bumped to v0.15.0 to match. Verified locally against baseline's actual check-embedder script: all 10 fragments (4 default + 6 release-please) pass.
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
1 participant
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.
Summary
rubykatzen/baselinepin fromv0.13.1tov0.15.0across all four reusable-workflow references (lint.yml,embedder.yml,github.yml,notify-telegram-pr.yml).extraembedder config for release-please conventions - opts in viaembedder.yml's newextra: '["release-please"]'input.release-please-config.jsonkeys we didn't have (include-component-in-tag: false,pull-request-title-pattern: "chore: release ${version}") and apr.ymlworkflow runningamannn/action-semantic-pull-requestto lint PR titles - added both.chore(main): release X.Y.Ztochore: release X.Y.Z(release-please's default component-scoped pattern vs. baseline's plain one) - updated AGENTS.md's CI/CD section to match.embedded-fragmentsfragment content changed wording slightly (mentions the newextrainput) - updated AGENTS.md to match verbatim.Test plan
check-embedderscript (check.pyfromrubykatzen/baseline@v0.15.0) locally against this working tree withEXTRA='["release-please"]'- all 10 fragments pass (4 default + 6 release-please)pre-commit run --all-filespasses (yamllint, pymarkdown, ruff, actionlint)release-please-config.jsonvalidated as well-formed JSON