Skip to content

Conversation

@skrawcz
Copy link
Contributor

@skrawcz skrawcz commented Oct 11, 2025

This should only move apache-hamilton* artifacts.

We should only create apache-hamilton artifacts for the source release vote.
We can post-process for upload to pypi.

Also contains update to docs for the release to include links to the downloads.

Changes

  • adds to scripts

How I tested this

  • did release with it

Notes

Checklist

  • PR has an informative and human-readable title (this will be pulled into the release notes)
  • Changes are limited to a single goal (no scope creep)
  • Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future TODOs are captured in comments
  • Project documentation has been updated if adding/changing functionality.

This should only move apache-hamilton* artifacts.
This will make it simpler to release things. Since we vote on
source releases -- this will make it simpler to do so rather
than much post-processing.

Note: flit for some reason creates metadata that is ahead of
what twine knows about.

This then updates the helper to drop worrying about the other
artifacts. We'll postprocess them to upload to pypi.
@skrawcz skrawcz changed the title Adds script to help promote RC artifacts Adds script to help promote RC artifacts & modifies packages for future source releases Oct 13, 2025
We should move files to save on disk space.
We missed this in the initial ASF setup.
"""Creates the source tarball, GPG signature, and checksums using `python -m build`."""
print("Creating release artifacts with 'python -m build'...")
files_to_upload = []
print("Creating release artifacts with 'flit build'...")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we remove the print and use echo in the .sh script instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is closer to the code -- so no difference?

@skrawcz skrawcz requested a review from zilto October 27, 2025 06:33
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.

3 participants