Skip to content

fix: semantic release fix attempt#39

Merged
cjumel merged 3 commits into
mainfrom
cj/fix_semantic_release
Sep 15, 2025
Merged

fix: semantic release fix attempt#39
cjumel merged 3 commits into
mainfrom
cj/fix_semantic_release

Conversation

@cjumel
Copy link
Copy Markdown
Contributor

@cjumel cjumel commented Sep 13, 2025

Description

This PR attempts at fixing some issues with the semantic release. It also makes other CI/CD improvements.

Fixes

  • I made sure the whole commit history is checked out in the CI/CD workflow (this should fix the failing job, but I couldn't test that)
  • I enable a semantic release parameter to allow 0.x.x versions, to avoid bumping unwillingly to 1.0.0 (the one already set was not doing that exactly)

Improvements

  • I updated the github actions we used
  • I removed the tests on push on main for two reasons: even if they are failing, they are not currently preventing the release, so this is not very useful, and I enabled the settings to make sure all PRs have an up-to-date base branch, so these tests are redundant with the PRs one

Checklist

  • I have run the tests locally with make install-dev and make test
  • I have updated the README.md if my changes affected it
  • I have updated the package version in linkup/_version.py and pyproject.toml if I plan on creating a new release

@cjumel cjumel merged commit d811306 into main Sep 15, 2025
2 checks passed
@cjumel cjumel deleted the cj/fix_semantic_release branch September 15, 2025 08:42
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.

2 participants