-
Notifications
You must be signed in to change notification settings - Fork 9
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
Automate updates to browserslist #194
Labels
Milestone
Comments
Closed
I removed the issue label as this is a stand-alone issue, not part of a release. |
Found this StackOverflow that has a compelling option. Install the npm packages as dependencies and they will get updated with the regular chore deps updates. |
blackfalcon
added
auro-generator
not-reviewed
Issue has not been reviewed by Auro team members
labels
Oct 13, 2021
braven112
removed
the
not-reviewed
Issue has not been reviewed by Auro team members
label
Dec 21, 2021
blackfalcon
added
the
not-reviewed
Issue has not been reviewed by Auro team members
label
Jan 20, 2023
Suggestion: we could create a npm task for |
jason-capsule42
removed
Type: Feature
New Feature
not-reviewed
Issue has not been reviewed by Auro team members
labels
Oct 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As any repo ages, resources also age. But whenever a repo runs the
build
command, an alert goes by unnoticedWe can't influence where this shows up, but we should have a better way to ensure that this lib is updated.
Describe the solution you'd like
Somewhere in a build pipeline or with a pre-commit, it would be great if we could work in the following command to ensure that our test environments are always up to date.
The text was updated successfully, but these errors were encountered: