starred/pocket-id-pocket-id-1
1
0
Fork 0
mirror of https://github.com/pocket-id/pocket-id.git synced 2025-12-09 14:53:00 +03:00
Code Issues 122 Packages Projects Releases 10 Wiki Activity

[PR #577] [MERGED] Tag container images with v{major} #735

New Issue
Open
opened 2025-10-08 00:16:12 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2025-10-08 00:16:12 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pocket-id/pocket-id/pull/577
Author: @max-baz
Created: 5/27/2025
Status: ✅ Merged
Merged: 5/27/2025
Merged by: @stonith404

Base: main ← Head: patch-1

📝 Commits (1)

  • b3b5313 Tag container images with v{major}

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 .github/workflows/release.yml (+1 -0)

📄 Description

I'd like to enable auto-update on PocketID container, which would periodically fetch v1 tag, and pull all the future releases, like v1.0.1, v1.1.0, v1.3.7, etc - any future releases up to a point when you cut the next v2 with breaking changes.

Right now we have to either use v1.0 and manually keep track of when v1.1 gets released and manually updating the tag, or use latest and have the app break whenever the next major version is released.

Thanks!

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/pocket-id/pocket-id/pull/577 **Author:** [@max-baz](https://github.com/max-baz) **Created:** 5/27/2025 **Status:** ✅ Merged **Merged:** 5/27/2025 **Merged by:** [@stonith404](https://github.com/stonith404) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`b3b5313`](https://github.com/pocket-id/pocket-id/commit/b3b53133003b64e5791850c8db99db754c4cad07) Tag container images with v{major} ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+1 -0) </details> ### 📄 Description I'd like to enable auto-update on PocketID container, which would periodically fetch `v1` tag, and pull all the future releases, like `v1.0.1`, `v1.1.0`, `v1.3.7`, etc - any future releases up to a point when you cut the next `v2` with breaking changes. Right now we have to either use `v1.0` and manually keep track of when `v1.1` gets released and manually updating the tag, or use `latest` and have the app break whenever the next major version is released. Thanks! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2025-10-08 00:16:12 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
breaking
bug
documentation
feature
needs more upvotes
open to pull requests
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pocket-id-pocket-id-1#735
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?