Skip to content

fix(release-please): bump action to v5.0.0-oce.2 (uv.lock support) - #23

Merged
kojiromike merged 1 commit into
mainfrom
kojiromike/bump-release-please-action
Aug 27, 2026
Merged

fix(release-please): bump action to v5.0.0-oce.2 (uv.lock support)#23
kojiromike merged 1 commit into
mainfrom
kojiromike/bump-release-please-action

Conversation

@kojiromike

Copy link
Copy Markdown
Contributor

Bumps the reusable workflow to release-please-action@v5.0.0-oce.2 (tag on rebase/v5), whose rebuilt dist carries the release-please fork tip (69f51b7, 17.6.0 base) with the UvLock updater: python release PRs now bump the project's own version entry in uv.lock alongside pyproject.toml, so release tags no longer ship a lockfile uv sync --locked refuses — the oce-ensora-adapter v1.0.0 no-image bug (openCoreEMR/oce-ensora-adapter#41).

Action rebuild gate: npm test under node 24 — 22 passing, 0 failing; dist/index.js grep uv\.lock — 7 matches (0 in -oce.1).

Follow-up once a release PR demonstrably bumps uv.lock: oce-ensora-adapter's Dockerfile reverts uv sync --frozen to --locked.

v5.0.0-oce.2 rebuilds the action dist against the release-please fork
tip (17.6.0 base): python release PRs now bump the project's own
version entry in uv.lock alongside pyproject.toml, so release tags no
longer ship a lockfile uv sync --locked refuses (the oce-ensora-adapter
v1.0.0 no-image bug).

Gate: actionlint — clean (exit 0).

Assisted-by: Claude Code
@kojiromike
kojiromike merged commit caf5a3a into main Aug 27, 2026
1 check passed
@kojiromike
kojiromike deleted the kojiromike/bump-release-please-action branch August 27, 2026 02:27
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