- 
                Notifications
    
You must be signed in to change notification settings  - Fork 2.8k
 
feat(artifacts): Default to latest tag if not provided #27253
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
base: main
Are you sure you want to change the base?
Conversation
63134b1    to
    a36f9b8      
    Compare
  
    | 
           [NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.  | 
    
a36f9b8    to
    728c5c0      
    Compare
  
    | 
           I would like to see some system tests of E2E test. podman artifact create foobar /PATH/TO/object  | 
    
| 
           Why is this in Draft? What is it waiting for?  | 
    
| 
           /approve  | 
    
| 
           [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ninja-quokka, rhatdan The full list of commands accepted by this bot can be found here. 
Needs approval from an approver in each of these files:
 
      Approvers can indicate their approval by writing   | 
    
728c5c0    to
    c70cbe2      
    Compare
  
    | 
           @ninja-quokka needs a rebase.  | 
    
This change implements a feature where podman artifacts will default to using the 'latest' tag if no tag is provided by the user. This aligns the behavior of artifacts with that of container images, providing a more consistent user experience. Fixes: containers#27083 Requires: containers/container-libs#409 Signed-off-by: Lewis Denny <lewisdenny@me.com>
c70cbe2    to
    ada7c2b      
    Compare
  
    
This change implements a feature where podman artifacts will default to using the 'latest' tag if no tag is provided by the user. This aligns the behavior of artifacts with that of container images, providing a more consistent user experience.
Fixes: #27083
Does this PR introduce a user-facing change?