Skip to content

Conversation

@raphlinus
Copy link
Collaborator

This updates the changelog and version numbers in preparation for a release of version 0.3.0.

This updates the changelog and version numbers in preparation for a release of version 0.3.0.
Just a small formatting change
Copy link
Member

@DJMcNab DJMcNab left a comment

Choose a reason for hiding this comment

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

A few details to fix, but I'm in favour of this release.

This is a good reminder that we need to write down this process, because there's a lot of subtlety. The reason not to at the moment is that we have a few changes in the pipeline (e.g. https://xi.zulipchat.com/#narrow/channel/419691-linebender/topic/Updating.20the.20changelog/near/542955500), plus the rest of that thread.

But it does keep coming up as something which trips us up.

CHANGELOG.md Outdated
Comment on lines 16 to 17
## [0.2.0][] (2025-08-26)

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
## [0.2.0][] (2025-08-26)

This seems to be a copy-paste error


## Added
## [0.3.0][] (2025-10-09)

Copy link
Member

Choose a reason for hiding this comment

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

The MSRV line from unreleased needs to be copied under this release.

CHANGELOG.md Outdated
This release has an [MSRV][] of 1.86.

## Added
## [0.3.0][] (2025-10-09)
Copy link
Member

Choose a reason for hiding this comment

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

There needs to be a corresponding link definition to the tag at the bottom of the changelog

Copy link
Member

Choose a reason for hiding this comment

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

The paragraph at the top of this file needs to be updated, to link to the new release (in both places, and the date needs updating).

(We realise that this is annoying, and do have plans to make this simpler, but we haven't applied them yet.)

[package]
name = "fearless_simd_gen"
version = "0.2.0"
version = "0.3.0"
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure this crate needs to have a version, but I guess bumping it doesn't do any harm either.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah, I saw the version, figured it should match, but it doesn't seem important.

Choose a reason for hiding this comment

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

I recommend setting all publish = false crates to version 0.0.0. That makes it obvious that it isn't currently being versioned.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

So I dug into this a bit. The version field is currently missing in fearless_simd_tests, but present in the other two unpublished crates (macros and gen). It used to be required, but is optional as of Rust 1.75. I think we should be consistent. I'm wondering whether it's better to elide the version field or set them explicitly to 0.0.0 in all three crates.

Mostly fixing links.
Copy link
Member

@DJMcNab DJMcNab left a comment

Choose a reason for hiding this comment

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

Thanks for taking this on! This looks good.

@raphlinus raphlinus added this pull request to the merge queue Oct 14, 2025
Merged via the queue into linebender:main with commit 0a3ac74 Oct 14, 2025
18 checks passed
@raphlinus raphlinus deleted the v0.3.0 branch October 14, 2025 14:50
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