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

chore: release 1.0.0 #62

Closed
wants to merge 1 commit into from
Closed

chore: release 1.0.0 #62

wants to merge 1 commit into from

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented Dec 22, 2019

🤖 I have created a release *beep* *boop*

1.0.0 (2021-08-31)

⚠ BREAKING CHANGES

Bug Fixes

  • deps: update dependency execa to v5 (#85) (4dff7f3)
  • deps: update dependency tar to v6 (#64) (8a276ea)
  • deps: update dependency tmp to v0.2.0 (#71) (0842582)
  • deps: update dependency tmp to v0.2.1 (#75) (93f2c81)
  • support node.js 10 and up (#67) (06ed421)

Code Refactoring

  • simplify the module, tests, and remove old interface (#57) (f692000)

This PR was generated with Release Please. See documentation.

@release-please release-please bot added autorelease: pending type: process A process-related concern. May include testing, release, or the like. labels Dec 22, 2019
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Dec 22, 2019
@release-please release-please bot closed this Jan 4, 2020
@release-please release-please bot reopened this Jan 4, 2020
@release-please release-please bot closed this Jan 28, 2020
@release-please release-please bot reopened this Jan 28, 2020
@release-please release-please bot closed this Jan 29, 2020
@release-please release-please bot reopened this Jan 29, 2020
@release-please release-please bot closed this Feb 6, 2020
@release-please release-please bot reopened this Feb 6, 2020
@release-please release-please bot closed this Feb 19, 2020
@release-please release-please bot reopened this Feb 19, 2020
@release-please release-please bot closed this Apr 26, 2020
@release-please release-please bot reopened this Apr 26, 2020
@release-please release-please bot closed this Apr 27, 2020
@release-please release-please bot reopened this Apr 27, 2020
@release-please release-please bot closed this May 1, 2020
@release-please release-please bot reopened this May 1, 2020
@release-please release-please bot closed this May 26, 2020
@release-please release-please bot reopened this May 26, 2020
@release-please release-please bot closed this Jun 10, 2020
@release-please release-please bot reopened this Jun 10, 2020
@release-please release-please bot closed this Jul 16, 2020
@release-please release-please bot reopened this Jul 16, 2020
@release-please release-please bot closed this Aug 20, 2020
@release-please release-please bot reopened this Aug 20, 2020
@release-please release-please bot force-pushed the release-v1.0.0 branch 2 times, most recently from 628e942 to c0da42b Compare May 30, 2021 01:11
@release-please release-please bot force-pushed the release-v1.0.0 branch 3 times, most recently from 7750ccf to edc0e91 Compare June 14, 2021 05:42
@ddelgrosso1
Copy link
Contributor

Going to close this as 1.0.0-2 was released and this is now 2 years old and I am prepping to release 2.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autorelease: closed cla: yes This human has signed the Contributor License Agreement. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants