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

Upgrade Error Prone fork 2.36.0-picnic-1 -> 2.36.0-picnic-2 #1499

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

Stephan202
Copy link
Member

@Stephan202 Stephan202 commented Jan 4, 2025

Suggested commit message:

Upgrade Error Prone fork 2.36.0-picnic-1 -> 2.36.0-picnic-2 (#1499)

This new release is published using GitHub Packages rather than
JitPack. This comes with a simpler release setup and a (hopefully) more
stable package repository. A minor downside is that GitHub Packages
require authenticated access, even for read access. The documentation
has been updated accordingly.

The new release is no longer published using a custom groupId, enabling
some build simplifications.

While there, some obsolete fork-related documentation and configuration
is dropped.

See:
- https://github.com/PicnicSupermarket/error-prone/releases/tag/v2.36.0-picnic-2
- https://github.com/PicnicSupermarket/error-prone/compare/v2.36.0-picnic-1...v2.36.0-picnic-2

This is possible thanks to PicnicSupermarket/error-prone@a3aaf7c. See the README update for the requisite local changes. In the context of this work I also filed s4u/setup-maven-action#112.

NB: There's still a dependency on JitPack for com.github.lhotari:reactor-error-prone. It appears that in the last few days JitPack is more stable again. Let's review this dependency if/when flakiness returns.

@Stephan202 Stephan202 added dependencies chore A task not related to code (build, formatting, process, ...) labels Jan 4, 2025
@Stephan202 Stephan202 added this to the 0.20.0 milestone Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Copy link
Member Author

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

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

Some context.

Comment on lines -212 to -213
Pending a release of [google/error-prone#3301][error-prone-pull-3301], this
flag must currently be used in combination with `-Perror-prone-fork`.
Copy link
Member Author

Choose a reason for hiding this comment

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

This should have been deleted in the context of #685.

Comment on lines -1647 to -1663
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<systemPropertyVariables>
<!-- Property used by `ErrorProneForkTest`
to verify fork identification. -->
<error-prone-fork-in-use>true</error-prone-fork-in-use>
</systemPropertyVariables>
</configuration>
</plugin>
Copy link
Member Author

Choose a reason for hiding this comment

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

This should have been deleted in the context of #685.

@Picnic-DevPla-Bot
Copy link
Contributor

Suggested commit message:

Upgrade Error Prone fork 2.36.0-picnic-1 -> 2.36.0-picnic-2

This new release is published using GitHub Packages rather than
JitPack. This comes with a simpler release setup and a (hopefully) more
stable package repository. A minor downside is that GitHub Packages
require authenticated access, even for read access. The documentation
has been updated accordingly.

The new release is no longer published using a custom groupId, enabling
some build simplifications.

While there, some obsolete fork-related documentation and configuration
is dropped.

See:
- https://github.com/PicnicSupermarket/error-prone/releases/tag/v2.36.0-picnic-2
- https://github.com/PicnicSupermarket/error-prone/compare/v2.36.0-picnic-1...v2.36.0-picnic-2

Copy link
Member

@rickie rickie left a comment

Choose a reason for hiding this comment

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

Non-blocking comment. This is quite a nice cleanup! Curious to see how the GHP performs 😄

We are moving from v2.36.0 to the non-prefixed one, right?

Packages][error-prone-fork-packages]. This fork generally contains a few
changes on top of the latest Error Prone release. Using this profile
generally requires passing `-s settings.xml`, with [suitably
configured][github-packages-auth] `GITHUB_ACTOR` and `GITHUB_TOKEN`
Copy link
Member

Choose a reason for hiding this comment

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

I can't find where the ACTOR comes from. Any reason we are not going for USERNAME? Maybe I'm misunderstanding 🤔.

Copy link
Member Author

Choose a reason for hiding this comment

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

This variable is documented here :)

Copy link
Contributor

@mohamedsamehsalah mohamedsamehsalah left a comment

Choose a reason for hiding this comment

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

🍴 🍴

@mohamedsamehsalah
Copy link
Contributor

Is anyone going to address the bot's attempt to steal Stephan's work? 😄

Screenshot 2025-01-10 at 15 42 32

@Stephan202
Copy link
Member Author

I'll file a copyright claim ;)

This new release is published using GitHub Packages rather than
JitPack. This comes with a simpler release setup and a (hopefully) more
stable package repository. A minor downside is that GitHub Packages
require authenticated access, even for read access. The documentation
has been updated accordingly.

The new release is no longer published using a custom groupId, enabling
some build simplifications.

While there, some obsolete fork-related documentation and configuration
is dropped.

See:
- https://github.com/PicnicSupermarket/error-prone/releases/tag/v2.36.0-picnic-2
- PicnicSupermarket/error-prone@v2.36.0-picnic-1...v2.36.0-picnic-2
@Stephan202 Stephan202 force-pushed the sschroevers/github-packages branch from a7426de to 08cf003 Compare January 10, 2025 15:27
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 merged commit 7b81dc4 into master Jan 10, 2025
16 checks passed
@Stephan202 Stephan202 deleted the sschroevers/github-packages branch January 10, 2025 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore A task not related to code (build, formatting, process, ...) dependencies
Development

Successfully merging this pull request may close these issues.

4 participants