-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature: implement @tmcb/check-engines #3
Labels
Comments
0-vortex
added a commit
that referenced
this issue
Dec 18, 2023
🎉 This issue has been resolved in version 1.0.6-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
github-actions bot
pushed a commit
that referenced
this issue
Dec 18, 2023
## [1.0.6](v1.0.5...v1.0.6) (2023-12-18) ### 🐛 Bug Fixes * correct ghcr docker based action tag detection and warn ([b34123f](b34123f)), closes [#5](#5) * correct github machine user ([71c9d3a](71c9d3a)), closes [#2](#2) * implement tmcb check engines ([a2757c5](a2757c5)), closes [#3](#3) * implement tmcb conventional commit ([e8b0526](e8b0526)), closes [#4](#4)
🎉 This issue has been resolved in version 1.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of change
🍕 Feature
Current behavior
current check engines script is from open-sauced and not updated in 2 years
Suggested solution
change to new @tmcb/check-engines
Additional context
No response
The text was updated successfully, but these errors were encountered: