Skip to content

Maintenance: Migrate to husky v9 syntax to remove deprecation warning #2130

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

Closed
1 of 2 tasks
hjgraca opened this issue Feb 23, 2024 · 2 comments · Fixed by #2131
Closed
1 of 2 tasks

Maintenance: Migrate to husky v9 syntax to remove deprecation warning #2130

hjgraca opened this issue Feb 23, 2024 · 2 comments · Fixed by #2131
Assignees
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@hjgraca
Copy link
Contributor

hjgraca commented Feb 23, 2024

Summary

image

When running init-environment command we get a deprecation notice for husky install command.
Husky has deprecated that command in favour of husky command and has new syntax for the hooks as well.

Why is this needed?

Prevent the display of deprecation notice and support new version to avoid issues when deprecated.

Which area does this relate to?

Automation

Solution

Update hooks and init-environment command.
Migration steps can be found on the release https://github.com/typicode/husky/releases/tag/v9.0.1

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.

@hjgraca hjgraca added triage This item has not been triaged by a maintainer, please wait internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Feb 23, 2024
@hjgraca hjgraca self-assigned this Feb 23, 2024
@dreamorosi dreamorosi linked a pull request Feb 23, 2024 that will close this issue
9 tasks
@dreamorosi dreamorosi added on-hold This item is on-hold and will be revisited in the future and removed triage This item has not been triaged by a maintainer, please wait labels Feb 23, 2024
@dreamorosi dreamorosi moved this from Triage to Next iteration in Powertools for AWS Lambda (TypeScript) Feb 23, 2024
@github-project-automation github-project-automation bot moved this from Next iteration to Coming soon in Powertools for AWS Lambda (TypeScript) Feb 28, 2024
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added pending-release This item has been merged and will be released soon and removed on-hold This item is on-hold and will be revisited in the future labels Feb 28, 2024
Copy link
Contributor

github-actions bot commented Mar 4, 2024

This is now released under v2.0.0 version!

@github-actions github-actions bot added completed This item is complete and has been merged/shipped and removed pending-release This item has been merged and will be released soon labels Mar 4, 2024
@dreamorosi dreamorosi moved this from Coming soon to Shipped in Powertools for AWS Lambda (TypeScript) Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Development

Successfully merging a pull request may close this issue.

2 participants