Skip to content

Add the latest tags for a new release - #911

Open
jmcarcell wants to merge 7 commits into
mainfrom
add-latest-tags-new-release
Open

Add the latest tags for a new release#911
jmcarcell wants to merge 7 commits into
mainfrom
add-latest-tags-new-release

Conversation

@jmcarcell

@jmcarcell jmcarcell commented Aug 16, 2026

Copy link
Copy Markdown
Member

Adds the latest package tags for the upcoming release, notably including the dependency on key4hep/EDM4hep#497 to make metadata work in k4FWCore and k4MarlinWrapper.

@madbaron

Copy link
Copy Markdown
Member

Just a minor note: if you could hold off making the new release until early next week it would be great.
There's an ongoing MAIA Hackathon that is spawning a few fixes and upgrades that I think would benefit the wider community as well, and it would be good to get these in.
(Of course no problem if you can't wait!)

@jmcarcell
jmcarcell force-pushed the add-latest-tags-new-release branch 2 times, most recently from c40d470 to e645d8c Compare August 20, 2026 18:11
@madbaron

madbaron commented Sep 1, 2026

Copy link
Copy Markdown
Member

I have a question for my education, in case you know: I saw the addition of the new LCContent tag and was happy about it. Then I looked at the tag and wondered about the numbering. Ultimately I clicked on https://github.com/PandoraPFAOrg/LCContent/releases/tag/v05-00-00 and saw that I made that tag?? How did this happen? Apart from not having done that, I'm fairly sure I don't even have write permission to the LCContent repo.

Was it part of some CI magic triggered by the last merged PR?

Edit: looking from the phone browser shows @jmcarcell as author, which makes more sense, but also raises other questions. Maybe this is a GitHub "feature"..

@jmcarcell

Copy link
Copy Markdown
Member Author

Fixed now, it was a lightweight tag.

@jmcarcell
jmcarcell force-pushed the add-latest-tags-new-release branch 2 times, most recently from 8c9a5a2 to 8392d9a Compare September 6, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants