-
Notifications
You must be signed in to change notification settings - Fork 9
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
build(node-version): raised the minimum required node-version to v14 #148
build(node-version): raised the minimum required node-version to v14 #148
Conversation
Nice work, @mikearche. It's not part of this PR, but related to your comment: I'm wondering if |
@mikearche When you get a chance, can you open a new issue for the |
I created an issue @MattSidor #149. I think we can also move it to a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The following commands need to be run in order for Husky to run the pre-commit scripts.
chmod ug+x .husky/*
chmod ug+x .git/hooks/*
package.json
Outdated
@@ -1,27 +1,26 @@ | |||
{ | |||
"name": "@alaskaairux/icons", | |||
"description": "Alaska Air and Auro Design System Icons", | |||
"version": "4.17.0", | |||
"version": "5.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not manually change the version number in the JSON file. This will get updated with the semantic release process.
Also, this does not warrant a MAJOR version release. This is not a feature release for the tool, but as you stated in the commit, this is a change to the build process.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. I went ahead and removed the "BREAKING CHANGE" portion of the commit, and reverted package version change. I also force-pushed so the changes could be tracked with the existing commit. As far as the chmod
changes, I went ahead and added it to the prepare
script.
SEMVER is only needed for customer-facing releases. This update has no effect to a consumer. Build changes are related to the repo and that is managed via Git versioning. |
build(deps): bump husky from 4.3.8 to 8.0.2 build(deps): bump @commitlint/cli from 11.0.0 to 17.2.0 build(deps): bump @commitlint/config-conventional from 11.0.0 to 17.2.0 build(deps): bump @semantic-release/git from 9.0.1 to 10.0.1 build(deps): bump @semantic-release/changelog from 5.0.1 to 6.0.1 chore(deps): pin @web/dev-server to 0.1.31 perf(deps): remove unnecessary package @semantic-release/npm
@mikearche can you add me to this repo? The Husky pre-commit is still not working.
|
Also, we remove the Node 12.x test dependency |
Interesting, the pre-commit hook is working for me. It could be a windows thing though. I shouldn't have any globally installed dependencies either. It fired off when I amended my commit. I added you to the repo. |
Changes to be committed: modified: .husky/commit-msg modified: .husky/pre-commit
@mikearche yeah, it's a linix thing |
Changes to be committed: modified: .github/workflows/testPublish.yml
🎉 This PR is included in version 4.17.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
I wanted to update
svgo
because in sdc we are getting warnings from one of it's dependencies. In order to updatesvgo
we need to use Node 14, and in order to upgrade to Node 14 this project needed to update husky.Fixes: #143 and #111
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
There are a lot of changes in this project, but they mostly have to do with
package.json
changes as well as husky pre-commit changes. I wanted to do the work to clean up the dependencies as much as possible, because as I said above I would love to update svgo.I pinned the unreleased package
@web/dev-server
in case there is a version release that causes things to break.I removed
@semantic-release/npm
because I noticed that it was already a dependency of @semantic-release.I also updated
@semantic-release
as well as it's dependencies to the latest version since we can do that now that we only support Node 14 or higher.I'm also following semver, for updating the package version to 5.0.0 because requiring Node 14 or higher is a breaking change.
Useful links:
https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v8
Type of change:
Checklist:
By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team