Skip to content

Update version to 60.1.0 and add CHANGELOG - #11750

Merged
Jefffrey merged 7 commits into
apache:mainfrom
alamb:alamb/prepare_60.1.0
Oct 23, 2026
Merged

Jefffrey merged 7 commits into
apache:mainfrom
alamb:alamb/prepare_60.1.0

Conversation

@alamb

@alamb alamb commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

Prepare for the 60.1.0 release

What changes are included in this PR?

  1. Update version to 60.1.0
  2. Add 60.1.0 CHANGELOG (see rendered version https://github.com/alamb/arrow-rs/blob/alamb/prepare_60.1.0/CHANGELOG.md)

Are these changes tested?

By CI

Are there any user-facing changes?

New version and changelog

@alamb
alamb marked this pull request as ready for review October 22, 2026 09:07
@alamb
alamb requested a review from Jefffrey October 22, 2026 09:08

@Jefffrey Jefffrey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

one minor thing i noticed, is i ran cargo semver-checks manually and it picked up we added an enum variant as part of

    Checking parquet-variant v60.0.0 -> v60.1.0 (minor change)
     Checked [   0.006s] 202 checks: 201 pass, 1 fail, 0 warn, 58 skip

--- failure enum_variant_added: enum variant added on exhaustive enum ---

Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/enum_variant_added.ron

Failed in:
  variant VariantPathElement:ListElement in /Users/jeffrey/Code/arrow-rs/parquet-variant/src/path.rs:173

     Summary semver requires new major version: 1 major and 0 minor checks failed

im not sure if we want to be strict with this or its probably fine?

@alamb

alamb commented Oct 22, 2026

Copy link
Copy Markdown
Contributor Author

one minor thing i noticed, is i ran cargo semver-checks manually and it picked up we added an enum variant as part of

I am not sure -- I asked on the ticket

@Jefffrey Jefffrey added the development-process Internal changes; PRs with this label are excluded from changelog label Oct 22, 2026
@Jefffrey

Copy link
Copy Markdown
Contributor

once #11831 is merged ill update this, merge it in and create the RC

@github-actions github-actions Bot removed the development-process Internal changes; PRs with this label are excluded from changelog label Oct 23, 2026
@Jefffrey
Jefffrey enabled auto-merge October 23, 2026 23:17
@Jefffrey

Copy link
Copy Markdown
Contributor

@alamb @sdf-jkl @Rich-T-kid i ask no other PRs are merged before this one gets into the merge queue (dev process related PRs exempt as they dont impact released artifact or changelog)

once this is enqueued (and hopefully merged to main successfully) i can create the rc from the commit, so other PRs can then merge (and wont be part of 60.1.0 release)

@Jefffrey
Jefffrey added this pull request to the merge queue Oct 23, 2026
Merged via the queue into apache:main with commit b391e5a Oct 23, 2026
34 of 35 checks passed
@alamb

alamb commented Oct 23, 2026

Copy link
Copy Markdown
Contributor Author

Thank you @Jefffrey

Amazing it merges in 2 minutes1

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