Update the Python package to 1.4.1

[loalan]

Since 1.4.1 is the official latest version, @antoninbas - can the Pipy package be easily updated with this version?

[antoninbas]

In theory we just need to create Github tag (e.g., v0.0.4) and the Github workflows should take care of the rest. I can create the tag but I worry that something might have become stale / broken, and I would not have time to look into it :(

@jafingerhut Do you want to take a stab at creating a v0.0.4 locally and pushing it, to see if the PiPy workflow still works?

[jafingerhut]

I have attempted to create a PR that adds a Github tag of v0.0.4 here: #139

but I am not sure whether I have done the tagging part correctly. I do not have permission to merge it without review.

[antoninbas]

@jafingerhut I don't see a new tag: https://github.com/p4lang/p4runtime-shell/tags

Commands should be something like this:

git tag -a v0.0.4 -m "Version 0.0.4 - P4Runtime 1.4.1"
git push upstream v0.0.4    # Use the correct remote name (could be origin), but push to this repo and not to your fork (if you have one)

I also wouldn't update the README if I were you, or you'll have to make sure it stays accurate / up-to-date :/

[jafingerhut]

@jafingerhut I don't see a new tag: https://github.com/p4lang/p4runtime-shell/tags

Commands should be something like this:

git tag -a v0.0.4 -m "Version 0.0.4 - P4Runtime 1.4.1"
git push upstream v0.0.4    # Use the correct remote name (could be origin), but push to this repo and not to your fork (if you have one)

I also wouldn't update the README if I were you, or you'll have to make sure it stays accurate / up-to-date :/

I am pretty sure that what I did was this, in my fork:

git checkout -b create-tag-v0.0.4
git tag -a v0.0.4
git push --set-upstream origin create-tag-v0.0.4

Then when I went to Github, there was no button to click on to create a PR from that change.

I just tried your recommended commands on a clone I made of the original repo, NOT my fork, but I don't think I have permission to push to this repo directly.

[antoninbas]

You have admin permissions for this repo.
You need to push the tag directly. A tag is a different object from a branch, and there is no PR involved.

[alaahl]

Hi,
any update on this?

[jafingerhut]

@jafingerhut I don't see a new tag: https://github.com/p4lang/p4runtime-shell/tags

Commands should be something like this:

git tag -a v0.0.4 -m "Version 0.0.4 - P4Runtime 1.4.1"
git push upstream v0.0.4    # Use the correct remote name (could be origin), but push to this repo and not to your fork (if you have one)

I also wouldn't update the README if I were you, or you'll have to make sure it stays accurate / up-to-date :/

I have just done:

git clone git@github.com:p4lang/p4runtime-shell
git tag -a v0.0.4 -m "Version 0.0.4 - P4Runtime 1.4.1"
git push origin v0.0.4

and there were no errors.

I do not know yet where to check whether this is causing any Github workflows to run, since I believe there was no PR associated with the push.

[jafingerhut]

I found this under the Github 'Actions" tab that appears to have been executed as a result of my push mentioned in the previous comment: https://github.com/p4lang/p4runtime-shell/actions/runs/17191552119/job/48767853587

A couple of minutes later, I find that I can do pip install p4runtime-shell==0.0.4, and it installs that version.

I will close this issue, since it seems completed.

[alaahl]

Yes, I see the new version as well, thanks a lot!

[loalan]

Thanks Andy & Antonin!