the records I overrode back in May are still there, with an expiration date of
2999-01-31 15:00:00. They were superseded on May 23rd; superseded means that something else was released with that branch, and that obsoletes the entries with the tweaked expiration date.
I can re-jiggle the expiration date for what’s currently published in those branches, just want to clarify how this works. Branches sound like “containers of releases” but they’re really not - they are more of a “tag” for a release, and it’s on that “tag” that we set the expiration date. Further, when you do a new release, it doesn’t update the branch (tag), but creates a new one superseding the previous one. So if you release, even the same revision, with a branch, it will “reset” the expiration times we had configured on the previous release entry.
So per the above, one might think that once I change the expiration time on a branch, any release to that branch will keep the long expiration time (container branch), but in reality, a re-release resets the expiration time (newly-created tag).
Just keep the above in mind: long-lived branches are meant to be exactly that - long-lived, with the same release, and you should not release anything else to them if you want to keep the long expiration.
Let me know of the branches you need us to fix and I’ll gladly update the expiration dates again.