chore(migrate): release 1.0.0 - #31372
Merged
Merged
Conversation
Promotes @ionic/migrate from the 0.1.0 bootstrap publish to its first stable release. Version-only change; no source or behavior changes.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Issue number: internal
What is the current behavior?
@ionic/migrateis on npm at0.1.0, the manual bootstrap publish that was needed to create the package page so a trusted publisher could be registered. Bothlatestandnextpoint at it.What is the new behavior?
Bumps
packages/migrate/package.jsonand its lockfile to1.0.0so the release workflow can publish the first stable version.release-orchestrator.ymlwithrelease-type: migrate,tag: latest, againstmajor-9.0.packages/migratestays out oflerna.json, so this version is independent of the framework version.Pre-flight against this branch, matching what
release-migrate.ymlruns:npm run lint(tsc --noEmit): cleannpm test: 137 passed across 15 filesnpm run build: cleannpm pack --dry-run: 106 files,dist/pluspackage.jsonandREADME.mdonlyDoes this introduce a breaking change?
Other information
The publish workflow is scoped to
working-directory: ./packages/migratefor every step, so it cannot publish core or any framework package. It also fails the run if the version is already on npm.