ci: fix stale cliff.toml remote owner (awslabs -> aws)#747
Open
JamBalaya56562 wants to merge 1 commit into
Open
ci: fix stale cliff.toml remote owner (awslabs -> aws)#747JamBalaya56562 wants to merge 1 commit into
JamBalaya56562 wants to merge 1 commit into
Conversation
JamBalaya56562
force-pushed
the
fix-changelog-workflow
branch
from
90226ba to
fdb45a4
Compare
Contributor
|
I also saw this pipeline issue. I would prefer to use release-plz action to refactor the release pipeline. |
git-cliff's GitHub API enrichment was pointed at the wrong owner (awslabs/aws-lambda-web-adapter), which 404s. Correct it to aws/aws-lambda-web-adapter so PR/author links resolve. Scope note: this PR originally also reworked the Changelog workflow to open a PR instead of pushing to protected main, but per maintainer feedback the release pipeline will be refactored with release-plz instead, so this PR is narrowed to the one obvious cliff.toml fix. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
JamBalaya56562
force-pushed
the
fix-changelog-workflow
branch
from
fdb45a4 to
3529758
Compare
JamBalaya56562
changed the title
Contributor
Author
|
Thanks for the steer, @bnusunny — agreed that moving the release pipeline to I've narrowed this PR down to just the one obvious fix: the stale |
JamBalaya56562
added a commit
to JamBalaya56562/aws-lambda-web-adapter
that referenced
this pull request
Jun 2, 2026
Replace the manual bump/tag/changelog release process with release-plz (https://release-plz.dev), per maintainer feedback on aws#747. Flow: on push to main, release-plz opens a Release PR that bumps the Cargo.toml version and updates CHANGELOG.md (reusing the existing cliff.toml via changelog_config). Merging that PR creates the v<version> git tag, publishes a GitHub Release, and runs cargo publish. Key details: - Uses a GitHub App token (actions/create-github-app-token), NOT the default GITHUB_TOKEN. This is required so the GitHub Release created by release-plz triggers release.yaml (on: release: types: [released]) -- the default token cannot trigger other workflows, which would silently skip the layer build / deploy / Docker publish. - Re-enables crates.io publishing (the crate was left at 0.9.1 while the repo moved to 1.0.x because the manual process forgot to publish). Auth via crates.io trusted publishing (OIDC), no long-lived token. - Deletes the changelog.yaml workflow, now superseded by release-plz. Maintainer prerequisites are documented in release-plz.yml: enable 'Allow GitHub Actions to create and approve pull requests', install a GitHub App (Contents + Pull requests R/W) and set RELEASE_PLZ_APP_ID / RELEASE_PLZ_APP_PRIVATE_KEY, and register the crates.io trusted publisher. RELEASE_PLZ_NOTES.md is temporary research context and will be removed before merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
JamBalaya56562
added a commit
to JamBalaya56562/aws-lambda-web-adapter
that referenced
this pull request
Jun 2, 2026
Replace the manual bump/tag/changelog release process with release-plz (https://release-plz.dev), per maintainer feedback on aws#747. Flow: on push to main, release-plz opens a Release PR that bumps the Cargo.toml version and updates CHANGELOG.md (reusing the existing cliff.toml via changelog_config). Merging that PR creates the v<version> git tag, publishes a GitHub Release, and runs cargo publish. Key details: - Uses a GitHub App token (actions/create-github-app-token), NOT the default GITHUB_TOKEN. This is required so the GitHub Release created by release-plz triggers release.yaml (on: release: types: [released]) -- the default token cannot trigger other workflows, which would silently skip the layer build / deploy / Docker publish. - Re-enables crates.io publishing (the crate was left at 0.9.1 while the repo moved to 1.0.x because the manual process forgot to publish). Auth via crates.io trusted publishing (OIDC), no long-lived token. - Deletes the changelog.yaml workflow, now superseded by release-plz. Maintainer prerequisites are documented in release-plz.yml: enable 'Allow GitHub Actions to create and approve pull requests', install a GitHub App (Contents + Pull requests R/W) and set RELEASE_PLZ_APP_ID / RELEASE_PLZ_APP_PRIVATE_KEY, and register the crates.io trusted publisher. RELEASE_PLZ_NOTES.md is temporary research context and will be removed before merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
JamBalaya56562
added a commit
to JamBalaya56562/aws-lambda-web-adapter
that referenced
this pull request
Jun 2, 2026
Replace the manual bump/tag/changelog release process with release-plz (https://release-plz.dev), per maintainer feedback on aws#747. Flow: on push to main, release-plz opens a Release PR that bumps the Cargo.toml version and updates CHANGELOG.md (reusing the existing cliff.toml via changelog_config). Merging that PR creates the v<version> git tag, publishes a GitHub Release, and runs cargo publish. Key details: - Uses a GitHub App token (actions/create-github-app-token), NOT the default GITHUB_TOKEN. This is required so the GitHub Release created by release-plz triggers release.yaml (on: release: types: [released]) -- the default token cannot trigger other workflows, which would silently skip the layer build / deploy / Docker publish. - Re-enables crates.io publishing (the crate was left at 0.9.1 while the repo moved to 1.0.x because the manual process forgot to publish). Auth via crates.io trusted publishing (OIDC), no long-lived token. - Deletes the changelog.yaml workflow, now superseded by release-plz. Maintainer prerequisites are documented in release-plz.yml: enable 'Allow GitHub Actions to create and approve pull requests', install a GitHub App (Contents + Pull requests R/W) and set RELEASE_PLZ_APP_ID / RELEASE_PLZ_APP_PRIVATE_KEY, and register the crates.io trusted publisher. RELEASE_PLZ_NOTES.md is temporary research context and will be removed before merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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
2 participants
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
Fix the stale
cliff.tomlGitHub remote owner so git-cliff's API enrichment resolves correctly.The repo lives at
aws/aws-lambda-web-adapter, notawslabs/..., so the old value pointed git-cliff's GitHub API lookups (PR / author enrichment) at the wrong owner.Scope change
This PR originally also reworked the
Changelogworkflow to open a PR instead of pushing to the protectedmainbranch. Per maintainer feedback, the release pipeline will instead be refactored usingrelease-plz, so that workflow rework is dropped here.The PR is now narrowed to the single obvious
cliff.tomlfix, leaving the broader release-pipeline redesign to therelease-plzeffort.