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.26.0 #515

Merged
merged 1 commit into from
Feb 9, 2021
Merged

chore: release 1.26.0 #515

merged 1 commit into from
Feb 9, 2021

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 1, 2020

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

1.26.0 (2021-02-08)

Features

  • automate creation of the first LTS release (#514) (53e68b4)
  • make --checkCI optionable for git-node-land (#528) (b0be3dd)

Bug Fixes

  • accommodate case changes in README header (e8ef932)
  • fetch most recent 100 commits (#520) (3c862d1)
  • throw on missing info during release prep (#519) (223d075)
  • v8: correct order of ternary (#513) (6dab341)
  • undefined failures & JSON error (2c0cf83)

This PR was generated with Release Please.

@github-actions github-actions bot force-pushed the release-v1.26.0 branch 2 times, most recently from 89448c2 to d10485f Compare November 5, 2020 17:38
@github-actions github-actions bot force-pushed the release-v1.26.0 branch 2 times, most recently from f3f397a to c630ff2 Compare February 7, 2021 16:26
@Trott
Copy link
Member

Trott commented Feb 8, 2021

Can we merge this so that the fix that just landed gets released/published?

@codebytere codebytere requested a review from a team February 8, 2021 20:04
@richardlau richardlau merged commit 059c138 into master Feb 9, 2021
@Trott Trott deleted the release-v1.26.0 branch February 9, 2021 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants