Skip to content

build: rework breaking changes tooling #12950

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

Merged
merged 1 commit into from
Sep 4, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Sep 2, 2018

  • Reworks the breaking change tslint rule to remove the logic that checks that there are no expired breaking changes.
  • Adds a new script that can be used to get an overview of the pending and expired breaking changes.

@crisbeto crisbeto added pr: merge safe target: patch This PR is targeted for the next patch release labels Sep 2, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 2, 2018
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM.

*/
task('breaking-changes', () => {
const cwd = process.cwd();
const configFile = ts.readJsonConfigFile(join(cwd, 'tsconfig.json'), ts.sys.readFile);
Copy link
Member

Choose a reason for hiding this comment

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

Would it be better to just refer to the build config's project directory?

I know that gulp always changes the CWD to the gulpfile directory

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah I'd say so, I didn't know that we had it configured somewhere.

@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 3, 2018
* Reworks the breaking change tslint rule to remove the logic that checks that there are no expired breaking changes.
* Adds a new script that can be used to get an overview of the pending and expired breaking changes.
@crisbeto crisbeto force-pushed the breaking-changes-rework branch from a111fa5 to 4bed263 Compare September 3, 2018 16:20
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn merged commit 0ab720a into angular:master Sep 4, 2018
jelbourn pushed a commit that referenced this pull request Sep 11, 2018
* Reworks the breaking change tslint rule to remove the logic that checks that there are no expired breaking changes.
* Adds a new script that can be used to get an overview of the pending and expired breaking changes.
@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 9, 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.

4 participants