Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ jobs:
with:
release-type: python
package-name: imednet
version-file: pyproject.toml
version-file: packages/core/pyproject.toml
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,8 +58,8 @@ Releases are fully automated and driven by merged PR titles:
```
3. Merge to `main` using **Squash and merge** so the PR title becomes the merged commit message.
4. The `Automated Release` workflow runs `release-please` on `main` pushes and opens/updates a
Release PR with calculated semantic version, changelog updates, and `pyproject.toml` version
updates.
Release PR with calculated semantic version, changelog updates, and `packages/core/pyproject.toml`
version updates.
5. Maintainers trigger publication by approving and merging the bot-created Release PR.

Configuration requirements:
Expand Down
3 changes: 2 additions & 1 deletion docs/contributing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,8 @@ Releases are fully automated and driven by merged PR titles:

3. Merge to ``main`` with **Squash and merge** so the PR title becomes the merged commit message.
4. The ``Automated Release`` workflow runs ``release-please`` on ``main`` pushes and opens/updates
a Release PR with semantic version and changelog updates.
a Release PR with semantic version, changelog updates, and ``packages/core/pyproject.toml``
version updates.
5. Maintainers trigger publication by approving and merging the bot-created Release PR.

Configuration requirements:
Expand Down
Loading