Merge branch 'main' into codex/fix-release-please-labeling

Author: roodboi

.github/.release-please-manifest.json

@@ -1,3 +1,3 @@
 {
-  ".": "0.1.1"
+  ".": "0.1.2"
 }

.github/workflows/conventional-pr.yml

@@ -24,8 +24,6 @@ addition to the global baseline instructions.
 ## Commits And Releases
 
 - Use Conventional Commits for commit subjects.
-- Keep pull request titles conventional as well; the release flow depends on
-  it.
 - Before touching release behavior or release automation, read
   [docs/releasing.md](docs/releasing.md).
 
@@ -34,4 +32,3 @@ addition to the global baseline instructions.
 - Do not commit local build outputs such as the root `stack` binary.
 - If a generated or built artifact appears repeatedly during normal work, add it
   to `.gitignore` in the same change that introduces the behavior.
-

AGENTS.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## [0.1.2](https://github.com/hack-dance/stack/compare/v0.1.1...v0.1.2) (2026-03-25)
+
+
+### Bug Fixes
+
+* parse userless scp remote aliases ([e75c389](https://github.com/hack-dance/stack/commit/e75c3896ed6de3b3a078d5be65e2c40f18e7a957))
+* push release tags with configured token ([71fc029](https://github.com/hack-dance/stack/commit/71fc02944baff130e2c2832ed221e9f83587e978))
+* resolve repo from remote during init ([38914b6](https://github.com/hack-dance/stack/commit/38914b69d5e7d2c9c9bbf0fc121a4b9abd8aa448))
+* resolve repo from remote during init ([ffc793d](https://github.com/hack-dance/stack/commit/ffc793d0efe4cb867fec02606ef453af99a1d2ed))
+* separate release tagging from release please ([37f9eb3](https://github.com/hack-dance/stack/commit/37f9eb3488fd4f02a1faf4545af64721e97e0aaf))
+
 ## [0.1.1](https://github.com/hack-dance/stack/compare/stack-v0.1.0...stack-v0.1.1) (2026-03-25)
 
 

CHANGELOG.md

@@ -1,11 +1,14 @@
 # Releasing
 
-This repo uses conventional commits plus `release-please` and `goreleaser`.
+This repo uses conventional commits on `main` plus `release-please` and
+`goreleaser`.
 
 ## Release model
 
-- Pull request titles should follow Conventional Commits.
-- Release-bearing changes should land on `main` via squash or rebase merges so the final commit subject stays conventional.
+- Release-bearing changes should land on `main` with conventional commit
+  subjects.
+- Prefer squash or rebase merges for release-bearing PRs so `main` keeps
+  parseable release commits.
 - `release-please` watches `main`, opens a release PR, updates `CHANGELOG.md`, and bumps the version manifest.
 - Merging the release PR triggers `tag-release`, which creates the Git tag from the merged release commit.
 - Tag pushes trigger `goreleaser`, which builds artifacts, creates the GitHub Release, and updates `hack-dance/homebrew-tap`.