[PR #797] [MERGED] Shorten snap version on tagged revisions #1701

New issue

Closed

opened 2026-05-05 07:59:49 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 07:59:49 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/debauchee/barrier/pull/797
Author: @maxiberta
Created: 7/14/2020
Status: ✅ Merged
Merged: 7/14/2020
Merged by: @shymega

Base: master ← Head: short-tags

📝 Commits (1)

ef769d4 Shorten snap version on tagged revisions

📊 Changes

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

View changed files

📝 snap/snapcraft.yaml (+1 -1)

📄 Description

Hi! Congrats on the new release. Are there plans to release the snap for v2.3.3? Afaict, CI is pushing builds to edge, so it's just a matter of promoting the latest build to stable (maybe candidate first?).

Confusingly, the latest build on edge currently has version 2.3.2-122-g3395cca9 instead of just v2.3.3; not sure why it didn't catch the new tag. Maybe it was tagged after the snap was built? In any case, even if it had worked, the resulting snap version would've been 2.3.3-0-g3395cca9. This branch should improve that and make the next tagged release shorter.

If you merge this, the resulting snap build on edge should have version 2.3.3-1-g12345678. Maybe then it can just be promoted to candidate and/or stable?

_{🔄 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/debauchee/barrier/pull/797 **Author:** [@maxiberta](https://github.com/maxiberta) **Created:** 7/14/2020 **Status:** ✅ Merged **Merged:** 7/14/2020 **Merged by:** [@shymega](https://github.com/shymega) **Base:** `master` ← **Head:** `short-tags` --- ### 📝 Commits (1) - [`ef769d4`](https://github.com/debauchee/barrier/commit/ef769d4802d60824121f4922cdaa3db34db5ee9b) Shorten snap version on tagged revisions ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `snap/snapcraft.yaml` (+1 -1) </details> ### 📄 Description Hi! Congrats on the new release. Are there plans to release the snap for v2.3.3? Afaict, CI is pushing builds to `edge`, so it's just a matter of promoting the latest build to `stable` (maybe `candidate` first?). Confusingly, the latest build on `edge` currently has version `2.3.2-122-g3395cca9` instead of just `v2.3.3`; not sure why it didn't catch the new tag. Maybe it was tagged *after* the snap was built? In any case, even if it had worked, the resulting snap version would've been `2.3.3-0-g3395cca9`. This branch should improve that and make the next tagged release shorter. If you merge this, the resulting snap build on `edge` should have version `2.3.3-1-g12345678`. Maybe then it can just be promoted to `candidate` and/or `stable`? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>