Skip to content

Conversation

@molguin92
Copy link
Contributor

@molguin92 molguin92 commented Jan 12, 2026

Cuts the initial public release of ecdysis (v1.0.0). Once this PR has been approved and merged, will (1) upload release artifacts; (2) upload the crate to crates.io; and (3) make the repository public.

@molguin92 molguin92 changed the title v1.0.0 Initial public release: v1.0.0 Jan 12, 2026
@molguin92 molguin92 force-pushed the mmunoz/release-1.0.0 branch from 2fed783 to 55397e6 Compare January 12, 2026 16:58
@molguin92 molguin92 force-pushed the mmunoz/release-1.0.0 branch from 55397e6 to b52ed61 Compare January 12, 2026 17:18
Generated with clippy --fix
@molguin92 molguin92 force-pushed the mmunoz/release-1.0.0 branch from b52ed61 to 538d440 Compare January 12, 2026 17:25
@molguin92 molguin92 force-pushed the mmunoz/release-1.0.0 branch from bab827f to 5ad671c Compare January 12, 2026 17:33
@molguin92 molguin92 added this to the Initial public release milestone Jan 12, 2026
@molguin92 molguin92 self-assigned this Jan 12, 2026
Comment on lines +2 to +9
1.0.0
- 2026-01-12 chore(style): cargo fmt
- 2026-01-12 chore(clippy): fix clippy lints
- 2026-01-10 chore: prepare for v1.0.0
- 2025-06-05 feat: don't run duplicate jobs on PRs
- 2025-06-05 feat: Github CI pipeline to build and test ecdysis
- 2025-06-05 fix: cargo-sort lint
- 2025-06-05 feat: initial public ecdysis commit
Copy link

@celeste-sinead celeste-sinead Jan 19, 2026

Choose a reason for hiding this comment

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

Consider adopting https://keepachangelog.com/en/1.1.0/ (which I found it by reference from https://doc.rust-lang.org/cargo/reference/publishing.html ) instead of just listing commits.

There probably isn't a whole lot to be said for 1.0.0, because there isn't a real diff baseline 🙃 - so the file would be something like

# Changelog

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.0] - 2026-01-20

The first public release of this crate.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good call-out and I agree. However, we currently have some hooks in place to generate the RELEASE NOTES from commit messages, and getting rid of that would require some minor code changes. I will file an issue in the repo and do it after the initial release :)

@molguin92 molguin92 merged commit 469b558 into main Jan 20, 2026
12 checks passed
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.

2 participants