How long does it take to update to the latest release?

[brunompicinini]

I've updated my repositary with a new release which, luckily, got recognized as Latest by Github.

But when I try to visit my @main link through jsdelivr, it still loaded my old release.

So I've tried purging that URL to reflect the changes, and it indeed removed that old release… but now loads the previous release!

So not sure how to make jsdelivr quickly load my latest release after I publish it…

Additionally, oddly, if I remove the @main tag, it indeed loads the correct latest version. So not sure how to make sure that when I load @main it actually loads my latest release.

Thanks in advance.

[MartinKolarik]

Please see https://github.com/jsdelivr/jsdelivr#github and https://github.com/jsdelivr/jsdelivr#github

[brunompicinini]

Thanks for the reply. Both links are the same. Perhaps you meant to link to the caching? Anyhow, I've read it all and, forgive me for not fully understanding, in which category does a repo@main file falls into? Is it version aliasing? If it is, it doesn't seem it took 7 days to refresh the file. I've just checked and it's already loading the correct version :)

So I'm still not sure what to expect. Basically what I have is:

1. I use the repo@main link on my sites to link to my .js file
2. Then I work new stuff on branches and pull&merge into the main one
3. Then I release and tag a new version for the main branch

When can I expect that jsdelivr will recognize the latest release and update the repo@main link? 12 hours?

Additionally, do I need to do anything besides waiting so that the main link gets automatically updated?

[MartinKolarik]

If you use a @main reference the releases are not relevant at all and it follows the branch caching behavior. If you used @latest the release caching behavior would apply (note that it's "up to 7", not "strictly 7" in that case).

[brunompicinini]

Ohhh I see. Thanks for the explanation! So if I use the @main version, I don't need to create a release for it and it should update in 12 hours (following the branch caching behavior). Great! That's what I need. Thanks again!