Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin jira to latest version 3.8.0 #269

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

pyup-bot
Copy link
Collaborator

This PR pins jira to the latest release 3.8.0.

Changelog

1.2.3

3. The tag **"Target"** should be `main`, the main branch.
3. The contents of the release should reference the PR reference and the individual who contributed. In some cases where maintainers take over a previous PR it is better practice to reference the name of the original submitter of the PR. e.g. The maintainer re-makes a PR based on a stale PR, the GHA would mention the maintainer by default as they created the PR, so the originator should be used.

Publishing the Release

1. Pressing the **Edit** button of the latest draft release and pressing the **'Publish release'** button will trigger the release process.
2. The release process will request an approver from the list of release approvers. These are the maintainers specifically added here: https://github.com/pycontribs/jira/settings/environments/333132378/edit. This release environment also limits the branches that can be deployed. To follow the tag version convention mentioned earlier.
3. Finally this will automatically trigger the release CI action (as defined in our repository), this uses the relevant repository secrets to publish to PyPI.
Links

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