Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare 2.24.0.dev0 #21412

Merged
merged 5 commits into from
Sep 18, 2024
Merged

Prepare 2.24.0.dev0 #21412

merged 5 commits into from
Sep 18, 2024

Conversation

huonw
Copy link
Contributor

@huonw huonw commented Sep 15, 2024

No description provided.

@huonw huonw added automation:release-prep Preparation for doing a release, created by automation category:internal CI, fixes for not-yet-released features, etc. labels Sep 15, 2024
@huonw huonw self-assigned this Sep 15, 2024
@huonw huonw marked this pull request as draft September 16, 2024 00:33
@huonw
Copy link
Contributor Author

huonw commented Sep 16, 2024

huonw added a commit that referenced this pull request Sep 16, 2024
This unblocks doing 2.24 dev releases while we get ourselves sorted and
upgrade OSes on CI.

Our current 2.23 builds are issuing the following warning, which becomes
an error for 2.24-versioned builds (like #21412):

```
14:44:14.41 [WARN] DEPRECATED: using Pants on macOS 10.15 - 11 is scheduled to be removed in version 2.24.0.dev0.

Future versions of Pants will only run on macOS 12 and newer, but this machine appears older (macOS-10.15.7-x86_64-i386-64bit).

You can temporarily silence this warning with the `[GLOBAL].allow_deprecated_macos_before_12` option. If you have questions or concerns about this, please reach out to us at https://www.pantsbuild.org/community/getting-help.
```

The underlying deprecation is that Pants 2.24..0.dev0 and newer will no
longer support running of Pants on macOS < 12, and that includes our own
in-repo builds. However, it's strictly more permissive to build on macOS
10.15 or 11, so we're "allowed" to do that even though it's after the
deprecation time.

Upgrading the runners properly is covered by #21413. The x86-64 change
is in #21417.
huonw added a commit that referenced this pull request Sep 16, 2024
This `py_hermetic_scripts` option was deprecated in #21181 in favour of
the new `py_non_hermetic_scripts_in_resolve` option. This was merged for
2.23.0.dev6 and thus will come in 2.23.0 soon-ish...

It seems to be very little code to support `py_hermetic_scripts` (just a
single extra clause in an `if` statement, plus the option definition
itself), so it seems unnecessarily aggressive to deprecate in one cycle.
This extends it a few releases to make it easier for users to test
pre-releases.

For instance, someone using 2.22.0 (current stable) with
`py_hermetic_scripts` can currently test 2.23.0a0 with just a warning
(e.g. adjust `pants_version` and run it through their CI), but would be
blocked from doing _any_ testing of 2.24.0.dev0 (#21412) until they fix
this option. That is, by removing the option quickly, it's harder for
them to validate any part of the 2.24 or 2.25 release series and provide
us feedback while on older versions.

(We're being more permissive than what we were previosuly communicating,
so I don't think we need release notes or to otherwise highlight it.)
@huonw
Copy link
Contributor Author

huonw commented Sep 16, 2024

@huonw huonw marked this pull request as ready for review September 16, 2024 17:37
@huonw huonw merged commit 06d4884 into main Sep 18, 2024
25 checks passed
@huonw huonw deleted the automation/release/2.24.0.dev0 branch September 18, 2024 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation:release-prep Preparation for doing a release, created by automation category:internal CI, fixes for not-yet-released features, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants