Skip to content

Conversation

ArturU043
Copy link
Contributor

Follow up on PR #588 and solution to #649

This workflow updates the pyproject.toml version to the new Github release tag and pushes it to the repo.
Also, it builds and publishes the PyPI distribution associated with the release version.

To bypass the push protection on master, I added:

  • Deploy key: Github Actions - protection bypass with write permits
    • Public key built with ssh-keygen -t ed25519 -C "deploy-key-to-front-end" -N ""
  • Secret: DEPLOY_KEY
    • Contains the private key
  • Added "Deploy Keys" to the Bypass list of the ProtectMaster ruleset

The workflow imports the ssh key from the secrets.DEPLOY_KEY and was tested on dev branches

The rule bypass was not tested yet on master

@ArturU043 ArturU043 self-assigned this Sep 5, 2025
Copy link

codecov bot commented Sep 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.19%. Comparing base (1413cd7) to head (2d819d6).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #652   +/-   ##
=======================================
  Coverage   97.19%   97.19%           
=======================================
  Files          29       29           
  Lines        1959     1959           
=======================================
  Hits         1904     1904           
  Misses         55       55           
Flag Coverage Δ
unittests 97.19% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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