Switch to new compas-actions - #89
Merged
Merged
Conversation
gonzalocasas
requested review from
WeiTing1991 and
chenkasirer
and
a lite review from Copilot
August 13, 2026 14:17
Contributor
There was a problem hiding this comment.
Pull request overview
Updates this repository’s CI/release automation to use the newer compas-dev/compas-actions workflows, shifting releases to a PR-driven process on merges to main (rather than local tagging / invoke release).
Changes:
- Reworked GitHub Actions workflows to use
compas-dev/compas-actionsfor CI, release preparation, publishing, GitHub release creation, and docs deployment. - Added PR-based release process documentation (
RELEASING.md) and linked it from the README. - Adjusted Invoke tasks and bumpversion settings to better fit the new automated release flow (including a
pre-buildtask for generating protobuf assets).
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
tasks.py |
Adds an invoke pre-build task to generate protobuf zip assets before release/build steps. |
RELEASING.md |
Documents the new PR-driven release process and required repo settings. |
README.md |
Links maintainers to the new release documentation. |
pyproject.toml |
Disables bumpversion auto-commit/tag to align with automated release PR workflow. |
.github/workflows/release.yml |
Replaces tag-triggered release with “detect release merge” + build/prepare/publish/create-release/docs jobs using compas-actions. |
.github/workflows/prepare-release.yml |
Adds a manual workflow_dispatch entrypoint to open a release PR via compas-actions. |
.github/workflows/pr-checks.yml |
Switches PR checklist validation to compas-actions release/changelog checks and introduces explicit permissions. |
.github/workflows/docs.yml |
Removes the bespoke docs deployment workflow (now handled via compas-actions in release.yml). |
.github/workflows/build.yml |
Updates CI to use compas-actions and adds an assets job that runs invoke pre-build and uploads generated zips. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+19
to
+21
| steps: | ||
| - uses: compas-dev/compas-actions/release-check@main | ||
| id: release |
Comment on lines
+20
to
+22
| steps: | ||
| - uses: compas-dev/compas-actions/release-check@main | ||
| id: release |
Comment on lines
+22
to
+24
| steps: | ||
| - uses: compas-dev/compas-actions/release-pr@main | ||
| with: |
Comment on lines
+10
to
+12
| permissions: | ||
| contents: read | ||
|
|
Comment on lines
+18
to
+19
| - uses: compas-dev/compas-actions/release-check@main | ||
|
|
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
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.
What type of change is this?
Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.CHANGELOG.mdfile in theUnreleasedsection under the most fitting heading (e.g.Added,Changed,Removed).invoke test).invoke lint).compas.datastructures.Mesh.