diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 757610f..435a775 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -54,6 +54,8 @@ jobs: run: node test/geometry.js - name: Overlay editor run: node test/editor.js + - name: Installable tree excludes agent instructions + run: test -z "$(git ls-files | grep -Ei '(^|/)(AGENTS|CLAUDE|GEMINI)\.md$' || true)" - name: Plugin manifest run: | jq -e '.schemaVersion == 1 and (.entryPoints | to_entries | all(.value as $p | ($p | test("^[^/].*") and (contains("..") | not))))' manifest.json diff --git a/AGENTS.md b/AGENTS.md deleted file mode 100644 index fbe9d67..0000000 --- a/AGENTS.md +++ /dev/null @@ -1,41 +0,0 @@ -# Repository workflow - -Read [docs/RELEASING.md](docs/RELEASING.md) before changing branches, CI, -release metadata, tags, GitHub settings, or marketplace submissions. - -## Branches and preservation - -- `main` is the default, stable installation branch. It is frozen at - `1ba0f8a30526f2148ff46885d67991862ae90f00` for marketplace issue #4893. - Do not push, merge, rebase, reset remotely, or add even documentation to it. -- Work on feature branches based on `develop`; target pull requests at `develop`. - Before editing, inspect `git status` and preserve existing uncommitted work. - Stage only your changes; never discard or commit unrelated user changes. -- Never force-push `main` or `develop`, move published tags, change the default - branch, disable protection, or bypass CI as a routine fix. -- Moving `main` or removing its freeze requires an explicit release instruction - from the owner. Ordinary implementation requests authorize development work, - not a release. Keep `main` locked between releases and throughout review. - -## CI and delivery - -- `.github/workflows/test.yml` defines the test commands. Keep CI running on - pushes to `develop` and `main`, and on pull requests. -- Run the relevant suites locally. Before merging, both GitHub checks `test` - and `windows-display-policy` must pass on the current PR revision. Fix - failures without weakening or skipping checks. Do not claim an unavailable - local platform check passed; use its GitHub runner. -- Local runtime installation (`./dev apply`, `./install.sh`) is separate from CI - and release publication. Do not run these merely to test a workflow change. -- Development CI must never automatically push to `main`, publish a release, - edit a marketplace issue, or install the plugin on the user's desktop. -- For an explicitly requested release, follow docs/RELEASING.md: prepare all - content and version changes first, promote once, record the resulting full - SHA, immediately freeze `main`, and obtain marketplace reports for that SHA. - A successful GitHub test run is not marketplace approval. -- After approval, keep developing on `develop`. A new `main` commit needs the - marketplace update process; an existing approval does not cover it. - -This file lives on `develop` because adding it to the currently frozen release -would change the exact commit the owner selected. GitHub protection enforces -the freeze independently of this file. diff --git a/CHANGELOG.md b/CHANGELOG.md index d0fb6eb..136ef6c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # Changelog +## 1.1.1 (2026-09-07) + +- Remove repository agent instructions from the installable plugin tree in + response to marketplace review. Maintainer instructions are kept outside + the plugin checkout. Runtime behavior is unchanged. + ## 1.1.0 (2026-09-06) - Scenes: save a workspace's layout together with what each zone holds: an diff --git a/docs/RELEASING.md b/docs/RELEASING.md index fcc62ce..afcfe95 100644 --- a/docs/RELEASING.md +++ b/docs/RELEASING.md @@ -3,13 +3,17 @@ ## Current candidate - Repository/default branch: `jdvmi00/hypertile`, `main`. -- Candidate: the `1.1.0` release, the merge of its release PR into `main`, - tagged `v1.1.0`. `main` is locked at that commit; its full SHA is recorded - here once the promotion has been read back. -- Submission: https://github.com/omacom/omarchy-plugin-marketplace/issues/4893 - (initial listing, pending). It supersedes the earlier candidate - `1ba0f8a30526f2148ff46885d67991862ae90f00` (manifest 1.0.1, marker tag - `marketplace-1ba0f8a`); leave that tag and the older `v1.0.1` tag alone. +- Release: `1.1.1`, tagged `v1.1.1` after promotion. The tag and the + maintainer notes on the submission record the exact promoted commit; + do not add a commit to `main` merely to record its own SHA. +- Submission: https://github.com/omacom/omarchy-plugin-marketplace/issues/5181 + (initial listing, pending). Issue #4893 is closed and superseded. +- Previous candidate: `25552c2a0ace46d74bff91390811c0ff73671b85` (`v1.1.0`). + Version 1.1.1 removes `AGENTS.md` from the installable tree. Preserve all + published tags, including `v1.1.0`, `v1.0.1`, and `marketplace-1ba0f8a`. +- Keep agent instruction files outside the repository and all installed + plugin contents. The complete repository tree is installed by the plugin + manager; an ignore rule alone does not remove tracked or local files. `main` is locked, including for administrators. It remains GitHub's default branch because marketplace validation and upstream installation resolve it. @@ -33,7 +37,7 @@ passing development PR from changing the candidate accidentally. ## Finish the current submission -1. Verify remote `main` still equals the candidate above and both its +1. Resolve the release tag to its full SHA, verify remote `main` matches, and confirm both its checks passed. 2. Update the existing submission's maintainer notes to describe this exact tree, including session recovery, background service, application launch, @@ -71,7 +75,7 @@ instruction before replacing this specifically selected SHA. 5. For an already listed plugin, use the marketplace's Plugin verification form, action **Verify and publish a newer upstream commit**, plugin ID `jmartin.hypertile`, repository root URL, and full current `main` SHA. - For an initial listing still pending, update #4893 instead. + For an initial listing still pending, update #5181 instead. 6. Wait for fresh compatibility and baseline reports, then maintainer approval and successful publication, all covering that same SHA. Keep `main` frozen throughout; continue development elsewhere. diff --git a/manifest.json b/manifest.json index 367f739..9843000 100644 --- a/manifest.json +++ b/manifest.json @@ -2,7 +2,7 @@ "schemaVersion": 1, "id": "jmartin.hypertile", "name": "Hypertile", - "version": "1.1.0", + "version": "1.1.1", "author": "Jim Martin", "description": "Zone-based tiling layouts for Hyprland's Lua layout API: browse and edit layouts at true scale in a fullscreen overlay, with a bar widget showing the current layout. Run install.sh after adding the plugin.", "kinds": [