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

feat: upgrade [email protected] #155

Merged
merged 1 commit into from
Feb 2, 2022

Conversation

xuatz
Copy link
Contributor

@xuatz xuatz commented Feb 2, 2022

Summary

Details

Workflow still works (fails) if the PR title is horrible

image

Notes

You might not be interested in this PR, but since I'm updating it to fix the "vulnerabilities" to comply with company regulations, I decide to make a PR just in case you want the changes.

Checklist

  • Fork the repo.
  • Create a PR in your own repo.
  • Create a PR to the upstream repo with the changes. In this case the preview workflow will fail, but we'll know that it works since you tested it in the fork. Please include a include a link to a workflow where you tested the current state of this pull request.

@xuatz xuatz force-pushed the feat/upgrade-semantic-release branch from 1c997c9 to b2fc056 Compare February 2, 2022 14:13
@xuatz xuatz marked this pull request as ready for review February 2, 2022 14:15
Copy link
Owner

@amannn amannn left a comment

Choose a reason for hiding this comment

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

Thank you very much also for this upgrade! The change looks good to me, but again, can you revert the change to the built file?

Potentially while you're at it, would you mind to leave a note about this in the contributors guide?

@xuatz xuatz force-pushed the feat/upgrade-semantic-release branch 2 times, most recently from 97f3daa to 9179e5f Compare February 2, 2022 16:04
@xuatz
Copy link
Contributor Author

xuatz commented Feb 2, 2022

Potentially while you're at it, would you mind to leave a note about this in the contributors guide?

I've added a line, but I'm not sure if I understood your intention or made the right wording ^^

CONTRIBUTORS.md Outdated
@@ -2,6 +2,8 @@

Thank you very much for contributing to this project!

Just a heads up, this project uses node16.
Copy link
Owner

Choose a reason for hiding this comment

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

Sorry, I should have been more precise. I meant if you can add a note at the bottom that the built file should not be included in the PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed to add the intended text instead 😆

@xuatz xuatz force-pushed the feat/upgrade-semantic-release branch from 9179e5f to b3307ec Compare February 2, 2022 16:10
@amannn
Copy link
Owner

amannn commented Feb 2, 2022

@xuatz The lockfile changed from your other PR, care to resolve that quickly? 🙂

@xuatz xuatz force-pushed the feat/upgrade-semantic-release branch from b3307ec to b13c44a Compare February 2, 2022 16:19
@amannn amannn merged commit ca264e0 into amannn:master Feb 2, 2022
@github-actions
Copy link

github-actions bot commented Feb 2, 2022

🎉 This PR is included in version 4.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants