starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-12 04:10:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[PR #977] [MERGED] Release: tag every release with develop #1786

New Issue
Closed
opened 2025-12-29 02:31:42 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:31:42 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/977
Author: @snh
Created: 11/16/2022
Status: ✅ Merged
Merged: 11/17/2022
Merged by: @juanfont

Base: main ← Head: develop-tag

📝 Commits (1)

  • 1639fad Release: tag every release with develop

📊 Changes

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

View changed files

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

📄 Description

  • read the CONTRIBUTING guidelines
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

Tags every new release, regardless of if it is a pre-release, with the develop tag. This means users will have four choices if they want to follow along without having to bump the container tag on every release:

  • latest: Latest stable release.
  • latest-debug: Latest stable release, in the debugging container.
  • develop: Latest release, regardless of if it is a beta or stable.
  • develop-debug: Latest release, regardless of if it is a beta or stable, in the debugging container.

🔄 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/juanfont/headscale/pull/977 **Author:** [@snh](https://github.com/snh) **Created:** 11/16/2022 **Status:** ✅ Merged **Merged:** 11/17/2022 **Merged by:** [@juanfont](https://github.com/juanfont) **Base:** `main` ← **Head:** `develop-tag` --- ### 📝 Commits (1) - [`1639fad`](https://github.com/juanfont/headscale/commit/1639fadac5ff88a967725f0147ae40f4c4b525b3) Release: tag every release with develop ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/release.yml` (+2 -0) </details> ### 📄 Description <!-- Please tick if the following things apply. You… --> - [x] read the [CONTRIBUTING guidelines](README.md#contributing) - [x] raised a GitHub issue or discussed it on the projects chat beforehand - [ ] added unit tests - [ ] added integration tests - [ ] updated documentation if needed - [ ] updated CHANGELOG.md <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> Tags every new release, regardless of if it is a pre-release, with the `develop` tag. This means users will have four choices if they want to follow along without having to bump the container tag on every release: - `latest`: Latest stable release. - `latest-debug`: Latest stable release, in the debugging container. - `develop`: Latest release, regardless of if it is a beta or stable. - `develop-debug`: Latest release, regardless of if it is a beta or stable, in the debugging container. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 02:31:42 +01:00
adam closed this issue 2025-12-29 02:31:42 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1786
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?