Repository navigation
Release 0.3.2 - #51
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.3.2: renames
## [Unreleased]inCHANGELOG.mdto## [0.3.2] - 2026-10-20, opens a fresh empty[Unreleased], and updates the compare links.What 0.3.2 contains
Changed
TestCredentialsinstead of being written intothe tests, and
tests/Architecture/NoLiteralCredentialsTest.phpfails the suite on any literalcredential left behind, so secret scanning has nothing to report. A second test there keeps
every generated credential's purpose a single plain word, because secret scanning reads a
compound purpose as the password itself. The
laranail/package-toolsfloor is now^0.1.10,the first release shipping that check.
After merge, the lightweight tag
v0.3.2goes on the merge commit, andrelease.ymlpublishes the GitHub release from this section.