This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
fix: ensures changelog files are up to date before adding entries #610
Conversation
This file contains 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
Monodeploy Publish PreviewThis Pull Request introduces the following changes: 3.7.3 "@monodeploy/changelog" (2023-03-09)Bug Fixes
3.7.3 "@monodeploy/git" (2023-03-09)Bug Fixes
3.7.3 "@monodeploy/node" (2023-03-09)Bug Fixes
3.7.3 "@monodeploy/publish" (2023-03-09)Bug Fixes
|
Codecov Report
@@ Coverage Diff @@
## main #610 +/- ##
==========================================
- Coverage 95.61% 95.52% -0.10%
==========================================
Files 54 54
Lines 1460 1475 +15
Branches 349 354 +5
==========================================
+ Hits 1396 1409 +13
- Misses 64 66 +2 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Addresses the changelog portion of #601. We move the changelog updates closer to the commit stage, and ensure we "refresh" the changelogs prior to prepending entries. This reduces the possibility of conflicts, assuming the pipeline running monodeploy takes appropriate measures to "lock" the publish stage (to limit concurrency). If a conflict is detected, we attempt a merge, preferring our changes over the remote.