Skip to content

Automate stable release workflow #6628

Open
@NoureldinYosri

Description

@NoureldinYosri

Description of the issue
The release process for stable cirq verions is currently a manual process documented in https://github.com/quantumlib/Cirq/blob/67090465ba60a1ba1fdb8926defa3a465d52cc22/release.md. This documentation is out of date because of changes to the underlying tools.

The release process doesn't have to be manual. we already automate the prelease process which packages and uploads cirq to pypi after each PR merge https://github.com/quantumlib/Cirq/blob/main/.github/workflows/release-main.yml.

A similar workflow should be created that gets triggered by a github realease ... that's the process for creating a stable release shoudl be just a two step operation: 1. update the cirq version 2. create a github release (Which triggers the realease workflow) which is what we do for other quantumlib libraries like QSim https://github.com/quantumlib/qsim/blob/master/.github/workflows/release_wheels.yml

Metadata

Metadata

Assignees

Labels

area/releasesgood first issueThis issue can be resolved by someone who is not familiar with the codebase. A good starting issue.kind/healthFor CI/testing/release process/refactoring/technical debt itemsno QC knowledge neededWant to contribute to Cirq, but don't know quantum computing? This issue is for you.triage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked on

Type

No type

Projects

Status

No status

Relationships

None yet

Development

No branches or pull requests

Issue actions