Skip to content

Conversation

Stephan202
Copy link
Member

@Stephan202 Stephan202 commented Mar 13, 2025

Suggested commit message:

Upgrade Arcmutate plugins (#1586)

These upgrades were not picked up automatically due to a groupId change.

Summary of changes:
- Upgrade Pitest Git plugins 1.1.4 -> 2.1.0
- Upgrade Arcmutate 1.2.2 -> 1.3.2
- Upgrade pitest-accelerator-junit5 1.0.6 -> 1.2.0

Hat tip to @jqno for his instructions here. Based on local testing I shouldn't rename the license file, but let's see what GitHub Actions thinks 👀

(Tested before and after results: no changes except that on this line there's now a surviving mutant instead of a MEMORY_ERROR mutant ✔️.)

@Stephan202 Stephan202 added this to the 0.21.0 milestone Mar 13, 2025
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.

🏹

@rickie rickie added chore A task not related to code (build, formatting, process, ...) dependencies and removed chore A task not related to code (build, formatting, process, ...) labels Mar 18, 2025
These upgrades were not picked up automatically due to a groupId change.

Summary of changes:
- Upgrade Pitest Git plugins 1.1.4 -> 2.1.0
- Upgrade Arcmutate 1.2.2 -> 1.3.2
- Upgrade pitest-accelerator-junit5 1.0.6 -> 1.2.0
@Stephan202 Stephan202 force-pushed the sschroevers/upgrade-arcmutate branch from 6825529 to 609af64 Compare March 18, 2025 10:35
Copy link

@Stephan202
Copy link
Member Author

With this change the posting of PR mutation changes is broken, but I suspect that this is because part of the logic is executed based on code on master. Let's merge this and see whether that fixes stuff. If not, I'll go debug.

@Stephan202 Stephan202 merged commit 854e05f into master Mar 18, 2025
16 checks passed
@Stephan202 Stephan202 deleted the sschroevers/upgrade-arcmutate branch March 18, 2025 10:47
@Stephan202
Copy link
Member Author

Let's merge this and see whether that fixes stuff.

Worked; see #1592.

Based on local testing I shouldn't rename the license file, but let's see what GitHub Actions thinks 👀

It appears that indeed things still work as expected. Post-merge build logs show that the license file is still picked up:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
Licenced for use in the development of open source software only.
Expires: 2025-10-27
For use with packages: tech.picnic.errorprone.*
See https://www.arcmutate.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

@Stephan202
Copy link
Member Author

W.r.t. the license file: follow-up in #1594.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants