Repository navigation
feat(changelog): parallelize regenerate and tolerate empty first commit - #32
Merged
Merged
Conversation
Analyze each unique ref once, in parallel (bounded by --concurrency), deduplicating by resolved commit hash. Skip the API diff for refs that cannot be analyzed (e.g. an empty initial commit without a pubspec) so the release still gets its commit-based entry.
Version AnalysisNext Version: Changelog: 📄 View detailed changelog in job summary Badge: |
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
1 participant
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.
Summary
--concurrency, default 4) when regenerating the changelog, deduplicating by resolved commit hash to avoid worktree path racespubspec.yaml): the affected release still gets its commit-based entry, just without an API Changes section, instead of crashingcompareApis(base, new)so diffs can be computed from already-resolvedPackageApis--concurrencyflag and document regenerate behavior in the READMEContext
Follow-up to the
--regeneratefeature. Running it on this repo crashed on the first release because the root commit had no analyzable Dart project.Test plan
dart test test/commands/changelog_command_test.dart(incl. new empty-initial-commit case)dart analyze