Skip to content

ci(release-please): bump action to v5.0.0-oce.3 #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kojiromike merged 1 commit into from
Sep 2, 2026
Merged

ci(release-please): bump action to v5.0.0-oce.3 #28

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release-please-reusable.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ jobs:

- name: Run Release Please
id: release
uses: openCoreEMR/release-please-action@v5.0.0-oce.2
uses: openCoreEMR/release-please-action@v5.0.0-oce.3
with:
config-file: ${{ inputs.config-file }}
manifest-file: ${{ inputs.manifest-file }}
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,4 +78,4 @@ Secrets:

Callers in the `openCoreEMR` org should use `secrets: inherit`. The reusable workflow reads the org variable `RELEASE_PLEASE_CLIENT_ID` (auto-inherited) and the org secret `RELEASE_PLEASE_PRIVATE_KEY` (forwarded by `inherit`), mints a short-lived App installation token, and uses it for checkout and release-please. PRs opened by the App identity trigger downstream `pull_request` workflows; PRs opened by the default `GITHUB_TOKEN` do not (GitHub anti-recursion).

The pinned action ref (`openCoreEMR/release-please-action@v5.0.0-oce.2`) is hardcoded — GitHub Actions does not allow expressions in `uses:` references, so it can't be a workflow input.
The pinned action ref (`openCoreEMR/release-please-action@v5.0.0-oce.3`) is hardcoded — GitHub Actions does not allow expressions in `uses:` references, so it can't be a workflow input.