Repository navigation
stable35: include dependency updates required by LibreSign stable35 - #103
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
…0.5.0 Update PDF signature validator to v0.5.0
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
chore(deps): update PDF signature validator to v0.5.1
Signed-off-by: André Maia <andrefnkmm@gmail.com> Assisted-by: Claude Code:claude-fable-5-1
Signed-off-by: André Maia <andrefnkmm@gmail.com> Assisted-by: Claude Code:claude-fable-5-1
Update jsignpdf-php to v3.0.0
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
…dator-0.5.2 chore: update pdf signature validator to 0.5.2
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.
Context
LibreSign/libresign:stable35currently references3rdpartycommit9b2d970391b802245dc2bcf8ee384ccf44d70bf3, but theLibreSign/3rdparty:stable35branch still points tocddfc39be9e5841421ffb954f919afc2ff6a9809.This happened because the LibreSign stable35 backports reused commits from the
3rdpartymain line instead of first advancing/backporting the corresponding dependency changes to3rdparty:stable35:cddfc39to63d763a, the head commit of3rdpartyPR Update jsignpdf-php to v3.0.0 #96 (main).63d763ato9b2d970, the merge commit of3rdpartyPR chore: update pdf signature validator to 0.5.2 #97 (main).A git submodule stores only a commit SHA, not a branch relationship, so Git allowed stable35 to reference those commits even though
3rdparty:stable35had never been advanced.What is between
cddfc39and9b2d970The range is a linear fast-forward of 9 commits containing four dependency updates and their merge commits:
6f5ccab- update PDF signature validator to v0.5.0c5f453b- merge 3rdparty Update PDF signature validator to v0.5.0 #94f6966f7- update PDF signature validator to v0.5.14615d2b- merge 3rdparty chore(deps): update PDF signature validator to v0.5.1 #95097e30e- update jsignpdf-php to v3.0.063d763a- regenerate scoped dependencies for jsignpdf-php 340a9894- merge 3rdparty Update jsignpdf-php to v3.0.0 #96804ba62- update PDF signature validator to v0.5.29b2d970- merge 3rdparty chore: update pdf signature validator to 0.5.2 #97These are the dependency-side changes required by the LibreSign stable35 backports #8260 and #8263. There are no unrelated later
mainchanges in this range.Change
Fast-forward
3rdparty:stable35fromcddfc39to9b2d970so that the stable branch actually contains the dependency commits already consumed byLibreSign/libresign:stable35.This does not introduce newer
mainchanges such as GeoIP2 or jsignpdf-php 3.2.0; those are after9b2d970.Validation
cddfc39...9b2d970is a strict fast-forward: 9 ahead, 0 behind.LibreSign/libresign:stable35already references9b2d970.stable34andstable33remain on their own corresponding3rdpartybranches/commits.