Should be `--version 1.0.0rc2` added to the command.

On Tue, Oct 28, 2025 at 11:11 PM Jens Scheffler <[email protected]> wrote:

> Followed the release checking guide and wanted to validate as my PMC
> duty but got the following error:
>
> (airflow) jscheffl@hp860g9:~/Workspace/airflow$ breeze
> release-management prepare-airflow-tarball --distribution-name
> apache_airflow_ctl
> Creating tarball for apache_airflow_ctl airflow-ctl/1.0.0
> fatal: not a valid object name: airflow-ctl/1.0.0
> Failed to create tarball
> /home/jscheffl/Workspace/airflow/out/apache_airflow_ctl-1.0.0-source.tar.gz
>
> for Apache apache_airflow_ctl airflow-ctl/1.0.0
> (airflow) jscheffl@hp860g9:~/Workspace/airflow$ git status
> HEAD detached at airflow-ctl/1.0.0rc2
> nothing to commit, working tree clean
>
> Any idea/guidance? Is this a teething breeze bug?
>
> On 28.10.25 07:54, Amogh Desai wrote:
> > Really nice to see this one fold in so quickly!
> >
> > Great amount of effort, Bugra and Jarek!
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, Oct 28, 2025 at 6:06 AM Buğra Öztürk <[email protected]>
> > wrote:
> >
> >> Wohooo! +1 non-binding
> >>
> >> Again and again couldn't share my good feelings. Amazing community, many
> >> thanks everyone being there for support, implement, test, release,  for
> >> everything 🎉🎉🙏
> >>
> >> Bugra Ozturk
> >>
> >> On Mon, 27 Oct 2025, 23:01 Jarek Potiuk, <[email protected]> wrote:
> >>
> >>> The release candidate for **Apache Airflow Ctl**: 1.0.0rc2  is now
> >>> available for testing!
> >>>
> >>> This email is calling for a vote on the release, which will last at
> least
> >>> until the
> >>> 23:00 CET, Friday, October 30, 2025 and until 3 binding +1 votes have
> >> been
> >>> received.
> >>>
> >>> Consider this my +1 (binding) vote.
> >>>
> >>> The apache-airflow-ctl 1.0.0rc2 package is available at:
> >>> https://dist.apache.org/repos/dist/dev/airflow/airflow-ctl/1.0.0rc2/
> >>>
> >>> The "apache-airflow-ctl" packages are::
> >>>
> >>>     - *apache_airfow_ctl-1.0.0-source.tar.gz* is a source release that
> >> comes
> >>>       with INSTALL instructions.
> >>>     - *apache_airfow_ctl-1.0.0.tar.gz* is the binary Python "sdist"
> >> release.
> >>>     - *apache_airfow_ctl-1.0.0-py3-none-any.whl* is the binary Python
> >> wheel
> >>> "binary" release.
> >>>
> >>> Public keys are available at:
> >>> https://dist.apache.org/repos/dist/release/airflow/KEYS
> >>>
> >>> Please vote accordingly:
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove with the reason
> >>>
> >>> Only votes from PMC members are binding, but all members of the
> community
> >>> are encouraged to test the release and vote with "(non-binding)".
> >>>
> >>> The test procedure for PMC members is described in:
> >>>
> >>>
> >>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOWCTL.md#verify-the-release-candidate-by-pmc-members
> >>> The test procedure for contributors and members of the community who
> >> would
> >>> like to test this RC is described in:
> >>>
> >>>
> >>
> https://github.com/apache/airflow/blob/main/dev/README_RELEASE_AIRFLOWCTL.md#verify-the-release-candidate-by-contributors
> >>> Please note that the version number excludes the 'rcX' string, so it's
> >> now
> >>> simply 1.0.0 for the apache-airflow-ctl package.
> >>> This will allow us to rename the artifact without modifying the
> artifact
> >>> checksums when we actually release.
> >>>
> >>> *Docs* (for preview):
> >>>
> >>
> https://airflow.staged.apache.org/docs/apache-airflow-ctl/1.0.0/index.html
> >>> *Release Notes*:
> >>>
> >>>
> >>
> https://github.com/apache/airflow/blob/airflow-ctl/1.0.0rc2/airflow-ctl/RELEASE_NOTES.rst
> >>> *Testing Instructions using PyPI*:
> >>>
> >>> The packages are available in PyPI:
> >>> https://pypi.org/project/apache-airflow-ctl/1.0.0rc2/
> >>>
> >>> You can build a virtualenv that installs this and other required
> packages
> >>> like this:
> >>>
> >>> uv venv
> >>> uv pip install -U apache-airflow-ctl==1.0.0rc2
> >>>
> >>> Regards,
> >>> Jarek & Bugra
> >>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to