Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop creating a patch for v5.3.1 upgrades on windows #41

Open
wants to merge 2 commits into
base: artifactrebase
Choose a base branch
from

Conversation

l0rd
Copy link

@l0rd l0rd commented Jan 15, 2025

Does this PR introduce a user-facing change?

Removes the windows installer patch for upgrading from v5.3.1 to v5.3.x that was introduced in containers#24827.

We need to do that because windows patches are allowed only for small and minor updates https://learn.microsoft.com/en-us/windows/win32/msi/patching-and-upgrades.

We also need to start blocking upgrades from v5.3.1 to v5.4, which will be implemented in a separate PR.

baude and others added 2 commits January 15, 2025 12:14
the podman artifact verb is used to manage OCI artifacts.  the following
verbs were added to `podman artifact`:

* add
* inspect
* ls
* pull
* push
* rm

Notable items with this PR:

* all artifact commands and their output are subject to change. i.e.
  consider all of this tech preview
* there is no way to add a file to an artifact that already exists in
  the store.  you would need to delete and recreate the artifact.
* all references to artifacts names should be fully qualified names in
  the form of repo/name:tag (i.e. quay.io/artifact/foobar:latest)
* i understand that we will likely want to be able to attribute things
  like arch, etc to artifact files.  this function is not available yet.

Many thanks to Paul Holzinger for autocompletion PRs and review PRs that
fixed issues early on.

Also fix up some Args function to specify the correct number of args.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Signed-off-by: Brent Baude <bbaude@redhat.com>
Removes the windows installer patch for upgrading
from v5.3.1 to v5.3.x that was introduced in
containers#24827.

We need to do that because windows patches are
allowed only for small and minor updates
https://learn.microsoft.com/en-us/windows/win32/msi/patching-and-upgrades.

We also need to start blocking upgrades from v5.3.1
to v5.4.x, which will be implemented in a separate commit.

Signed-off-by: Mario Loriedo <mario.loriedo@gmail.com>
@baude
Copy link
Owner

baude commented Jan 15, 2025

do you want to take this to the main branch and I can rebase to grab it ?

@l0rd
Copy link
Author

l0rd commented Jan 15, 2025

As you prefer. I have created a PR against main branch too.

@baude baude force-pushed the artifactrebase branch 3 times, most recently from 15911b8 to d2b1e08 Compare January 19, 2025 21:13
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