chore(release): 0.0.1 - #3
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Initial release, wave five of a nine-package batch.
What ships
Everything in the package so far, collected into one
## [0.0.1]section: the[Unreleased]section carried two### Addedheadings plusChangedandFixedbullets for code that has never been on pub.dev, so they are folded into what 0.0.1 does rather than listed as fixes to a release nobody had.MagicSentry.run,SentryServiceProvider<T>,SentryNetworkInterceptor,SentryUserContext<T>,EventBreadcrumbs(#2), and the install stub.Floors
magic ^0.0.22(live),sentry_flutter/sentry_dio^9.27.0.Publishing
The package does not exist on pub.dev yet, and the tag-triggered OIDC publish cannot create one. After merge the first upload runs by hand,
dart pub publishfrom the merge commit; then the0.0.1tag goes on that commit for history. Moving the package to the verified publisher and enabling automated publishing on its pub.dev admin page stays with the maintainer, after which the next tag publishes the usual way.Gates
dart format --output=none --set-exit-if-changed .11 files, 0 changed.flutter analyzeno issues.flutter test38 passed.dart pub publish --dry-run0 warnings.