Do not merge, targeting Jest 27 branch ATM to avoid future merge conflicts
Depends On: #44
Changes:
this commit upgrades np, the package the project uses for publishing, to
the latest version. this is a part of a larger effort in order to get
the dependencies of the project updated.
Testing:
I created a temporary script release-no: np --preview, which does a dry run of the publish. Note since I was working against a branch that wasn't master, I had to pass the --any-branch flag
npm run release-no -- --any-branch
> @stencil/eslint-plugin@0.3.1 release-no /Users/ryan/workspaces/stencil-eslint
> np --preview "--any-branch"
? The following new files will not be part of your published package:
- .github/workflows/CODEOWNERS
- .github/workflows/main.yml
- stencil-eslint-plugin-0.3.1.tgz
Continue? Yes
Publish a new version of @stencil/eslint-plugin (current: 0.3.1)
Commits:
- iwip 35e29af
- chore(dependencies): upgrade jest to v27 0685af0
- chore(github): update github actions (#42) ca186e3
- chore(github): add codeowners file (#43) 821016c
- fix(rule): add componentShouldUpdate to lifecycle declaration (#18) 43f832c
- Bump y18n from 4.0.0 to 4.0.3 (#40) d7c5edc
- Bump ini from 1.3.5 to 1.3.8 (#41) 060ef0e
- Bump tmpl from 1.0.4 to 1.0.5 (#39) 4af82bc
- Bump ws from 7.2.3 to 7.4.6 (#33) 827ccfe
- fix(typo): required-jsdoc typo (#22) 64e7124
- fix crash when can't find tag name 777b2f1
- Update readme fa0b4c4
Commit Range:
v0.3.1...master
Registry:
https://registry.npmjs.org/
? Select semver increment or specify new version prerelease 0.3.2-0
? How should this pre-release version be tagged in npm? next
✔ Prerequisite check
✔ Git
✔ Installing dependencies using npm
✔ Running tests using npm
↓ Bumping version using npm [skipped]
→ [Preview] Command not executed: npm version 0.3.2-0.
↓ Publishing package using npm [skipped]
→ [Preview] Command not executed: npm publish --tag next.
↓ Pushing tags [skipped]
→ Upstream branch not found; not pushing.
↓ Creating release draft on GitHub [skipped]
→ [Preview] GitHub Releases draft will not be opened in preview mode.
I also combed through the releases for NP, and couldn't find anything that looked like it would break us
Note:
This covers some of the work done in Major dependency updates #32 (but not all of it). The idea here is to split the upgrades up into separate chunks, where we group them by 'type'. Here, the publishing infrastructure is upgraded , but TypeScript and other dependencies didn't need to be updated in order to upgrade this infra
Do not merge, targeting Jest 27 branch ATM to avoid future merge conflicts
Depends On: #44
Changes:
this commit upgrades np, the package the project uses for publishing, to the latest version. this is a part of a larger effort in order to get the dependencies of the project updated.
Testing:
I created a temporary script
release-no: np --preview, which does a dry run of the publish. Note since I was working against a branch that wasn'tmaster, I had to pass the--any-branchflagI also combed through the releases for NP, and couldn't find anything that looked like it would break us
Note: This covers some of the work done in Major dependency updates #32 (but not all of it). The idea here is to split the upgrades up into separate chunks, where we group them by 'type'. Here, the publishing infrastructure is upgraded , but TypeScript and other dependencies didn't need to be updated in order to upgrade this infra