Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(schematics): make v6 migration work #10853

Merged
merged 1 commit into from Apr 16, 2018

Conversation

jelbourn
Copy link
Member

This includes:

  • Adding missing schema json to package
  • Add missing packageGroup entries to material, cdk, and moment-adapter
  • Move schematics for migration to the migrate-specific schema
  • Bump version to 6.0.0-rc.11

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 14, 2018
@@ -32,7 +32,7 @@ const allScssGlob = join(buildConfig.packagesDir, '**/*.scss');
const schematicsGlobs = [
// File templates and schemas are copied as-is from source.
join(schematicsDir, '**/+(data|files)/**/*'),
join(schematicsDir, '**/+(schema|collection).json'),
join(schematicsDir, '**/+(schema|collection|migration).json'),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

@jelbourn jelbourn Apr 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, good catch. Done.

@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Apr 14, 2018
@@ -20,7 +20,7 @@
"docs": "gulp docs",
"api": "gulp api-docs"
},
"version": "6.0.0-rc.5",
"version": "6.0.0-rc.11",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is it going from rc.5 to rc.11?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My guess is because this was published to NPM as rc.11 already, and this is an after-the-fact update

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep; it's not yet possible to test ng update without publishing to npm

This includes:
* Adding missing schema json to package
* Add missing packageGroup entries to material, cdk, and moment-adapter
* Move schematics for migration to the migrate-specific schema
* Bump version to 6.0.0-rc.11
Copy link
Contributor

@amcdnl amcdnl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba merged commit c9f5be6 into angular:master Apr 16, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants