tools-cicd
share cicd scripts
Running tool locally
Example:
AWS_PROFILE=dev-admin-terraform poetry run cicd --help
Release Procedures
- This project uses "trunk" based development off of
master. - PRs are allowed but always folded back to
master. - For now, releasing is manual, no automation.
- To release:
- Ensure all your features are ready on
master- You should not have any staged changes!
- In a terminal run
make version v={major|minor|patch}- Do not include a number! Poetry will auto-rev the value accordingly
- That's it
- This will create a new tag in Git ready for use
- Ensure all your features are ready on
Multi-Repository Release Coordination
The quest-v2 project includes a coordinated release script that allows you to trigger deployments across all related Quest v2 repositories simultaneously, rather than having to manually trigger each repository's release workflow individually.
Prerequisites
-
GitHub CLI: Install the GitHub CLI tool
# macOS brew install gh # Ubuntu/Debian sudo apt install gh # Windows winget install GitHub.cli
-
Authentication: Authenticate with GitHub
gh auth login
-
Script Setup: Navigate to the quest-v2 directory and make the script executable
cd quest-v2 chmod +x release-all.sh
Usage
From the quest-v2 directory, the script supports promoting from develop to qa:
# Promote to QA
./release-all.sh
# Show help and options
./release-all.sh --help
What it does
The script will:
- Trigger the "Release" workflow on all three Quest v2 repositories:
allfly-quest-uiallfly-quest-core-apigds-api
- Promote code from
developbranch toqa - Provide real-time status updates and links to monitor progress
- Display a summary of successful and failed releases
Monitoring
After triggering the releases, you can monitor progress through:
- The provided GitHub Actions URLs in the script output
- GitHub's Actions tab in each repository
- Your configured Slack notifications (if enabled)
Note: The script requires appropriate permissions to trigger workflows on all three Quest v2 repositories. Ensure your GitHub account has the necessary access rights.
1 maintainer
Metadata
1 maintainer
Release files for af-cicd 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| af_cicd-0.3.3.tar.gz | 56.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| af_cicd-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.1 kB
Release files / af_cicd-0.3.3.tar.gz
| Download URL | af_cicd-0.3.3.tar.gz |
|---|---|
| Size | 56.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbd391cc102e1de7605b6d25ff0985d1a10a7519cb34b719dfde9628a8936e3f
|
|
BLAKE2b-256 checksum How to use checksums |
55b30dbe52caea87a706cdbac078e4bce65c9c4c45d9b729b9f2b08f601bf43a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logRelease files / af_cicd-0.3.3-py3-none-any.whl
| Download URL | af_cicd-0.3.3-py3-none-any.whl |
|---|---|
| Size | 92.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a248de879b37ad670129daf036b07ec0546c489bce3b543a3239c172873dd5d
|
|
BLAKE2b-256 checksum How to use checksums |
5f8fc6c55c1b59d2586c22cc6246051f9a355b33c572ead94e9d038b0efd7f15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logSecurity for af-cicd 0.3.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for af_cicd-0.3.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
