@ije first of all thank you very much for your quick response to the issue yesterday (#1305), and for fixing it! We really appreciate it!
One thing I would like to understand is how are versions managed and released for esm.sh. I see in github workflows (https://github.com/esm-dev/esm.sh/blob/main/.github/workflows/production.yml and https://github.com/esm-dev/esm.sh/blob/main/.github/workflows/release.yml) that pushes to tags with v* get released, but from yesterday's incident I understand that rolling releases from main happen? Because the commit that caused the issue was not tagged with v* (nor included in changelog/release. One of the reasons why we did not catch this earlier was because the latest version (and tag) was for January 13 which did not contain the problematic commit. Should we assume going forward that whatever is on main is on prod?
Really appreciate all your work! Thank you again!
@ije first of all thank you very much for your quick response to the issue yesterday (#1305), and for fixing it! We really appreciate it!
One thing I would like to understand is how are versions managed and released for
esm.sh. I see in github workflows (https://github.com/esm-dev/esm.sh/blob/main/.github/workflows/production.yml and https://github.com/esm-dev/esm.sh/blob/main/.github/workflows/release.yml) that pushes to tags withv*get released, but from yesterday's incident I understand that rolling releases frommainhappen? Because the commit that caused the issue was not tagged withv*(nor included in changelog/release. One of the reasons why we did not catch this earlier was because the latest version (and tag) was for January 13 which did not contain the problematic commit. Should we assume going forward that whatever is onmainis on prod?Really appreciate all your work! Thank you again!