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 been developing automated release tooling that allows for releases from multiple branches. The goal being that you could support the main release line, along with back-porting security fixes to old majors, here's an example:
https://deno.land/x treats the most recent tag created as the latest release.
This means when I back-port a security fix to an ancient release line, Deno picks this release up.
Potential Solutions
detect that a repository is using a special -deno suffix for releases (I do this in yargs to differentiate between the Deno and JavaScript releases), if a repo uses a special suffix, ignore releases without suffix.
alternatively, perhaps sort the most recent releases?
The text was updated successfully, but these errors were encountered:
Background
I've been developing automated release tooling that allows for releases from multiple branches. The goal being that you could support the main release line, along with back-porting security fixes to old majors, here's an example:
yargs/yargs-parser@eab6c03
Problem
https://deno.land/x treats the most recent tag created as the latest release.
This means when I back-port a security fix to an ancient release line, Deno picks this release up.
Potential Solutions
-deno
suffix for releases (I do this in yargs to differentiate between the Deno and JavaScript releases), if a repo uses a special suffix, ignore releases without suffix.The text was updated successfully, but these errors were encountered: