ci: add moving minor tag

Release-As: 1.1.1

Author: hesreallyhim

.github/workflows/release-please.yml

@@ -27,8 +27,11 @@ jobs:
         if: ${{ steps.release.outputs.release_created }}
         run: |
           major="${{ steps.release.outputs.major }}"
-          tag="v${major}"
+          minor="${{ steps.release.outputs.minor }}"
+          tag_major="v${major}"
+          tag_minor="v${major}.${minor}"
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
-          git tag -f "$tag"
-          git push -f origin "$tag"
+          git tag -f "$tag_major"
+          git tag -f "$tag_minor"
+          git push -f origin "$tag_major" "$tag_minor"

docs/VERSIONING.md

@@ -135,11 +135,24 @@ engine-strict=true
 - Release Please runs on `push` to `main` (and manual dispatch).
 - Version tags:
   - `vX.Y.Z` (annotated release tag)
-  - `vX` (and optionally `vX.Y`) advanced on release
+  - `vX` and `vX.Y` moving tags, force-updated on each release
 
 **Rationale**
 - GitHub Action consumers should be able to pin to a major (`@v1`) while receiving compatible updates.
 - Release Please is the single source of truth for versions and changelogs.
+- Moving tags are managed by the release workflow via `git tag -f` + `git push -f` when a release is actually created.
+
+**Protocol**
+- Only the Release Please workflow updates `vX` and `vX.Y`.
+- Moving tags are updated only on release creation (not on release PR creation).
+- Do not create or move `vX`/`vX.Y` manually; if a manual release is needed, use a `Release-As: X.Y.Z` commit to drive Release Please.
+
+**Example (Release-As footer)**
+```
+chore: add social preview images
+
+Release-As: 1.1.1
+```
 
 ---
 

release-please-config.json

@@ -1,7 +1,7 @@
 {
   "packages": {
     ".": {
-      "release-type": "simple",
+      "release-type": "node",
       "package-name": "github-api-usage-monitor",
       "changelog-path": "CHANGELOG.md",
       "include-component-in-tag": false,