You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had to copy it a few times but I have a workflow that updates a single dependency after a repository dispatch from another repo after it releases a package to npm. It does a full update and will even bump major versions. Would be nice to not have to copy it. Maybe add an action here that takes a name of an NPM dependency and runs an update on it. Similar to update package lock but more targeted.
The text was updated successfully, but these errors were encountered:
I've had to copy it a few times but I have a workflow that updates a single dependency after a repository dispatch from another repo after it releases a package to npm. It does a full update and will even bump major versions. Would be nice to not have to copy it. Maybe add an action here that takes a name of an NPM dependency and runs an update on it. Similar to update package lock but more targeted.
The text was updated successfully, but these errors were encountered: