Promote dev to main: publish stable aegis-gitea-mcp 0.2.0 #66

Merged

Latte merged 3 commits from dev into main 2026-06-27 14:16:34 +00:00

Conversation 0 Commits 3 Files Changed 2

+101 -29

Bartender commented 2026-06-27 14:14:46 +00:00

Owner

Copy Link

Copy Source

What this does

Promotes dev to main. The substantive change carried over is the merge-based publishing pipeline in .gitea/workflows/publish.yml: the trigger moved from tag-only (v*) to push on dev and main, with per-branch package channels.

main still has the old tag-only publish workflow, which is why no package was ever produced (no v* tag was ever pushed). Merging this fixes that at the source.

What happens on merge

The new workflow lands on main, and the push to main triggers it immediately: lint, test, then publish the stable package aegis-gitea-mcp at 0.2.0 to the self-hosted Gitea PyPI registry. No tag required.

The pipeline is already validated on the dev channel: aegis-gitea-mcp-dev 0.2.0.dev243 published successfully.

Verify after merge

• The Actions run for this push is green (lint, test, publish).
• Stable package appears at https://git.hiddenden.cafe/Hiddenden/-/packages/pypi/aegis-gitea-mcp

Notes

• Version stays 0.2.0 (first stable publish, no conflict). Bump version in pyproject.toml first if you want a different stable number.
• Re-running main at the same version is a clean no-op: uv publish --check-url skips files already present in the registry.

## What this does Promotes `dev` to `main`. The substantive change carried over is the merge-based publishing pipeline in `.gitea/workflows/publish.yml`: the trigger moved from tag-only (`v*`) to push on `dev` and `main`, with per-branch package channels. `main` still has the old tag-only publish workflow, which is why no package was ever produced (no `v*` tag was ever pushed). Merging this fixes that at the source. ## What happens on merge The new workflow lands on `main`, and the push to `main` triggers it immediately: lint, test, then publish the stable package `aegis-gitea-mcp` at `0.2.0` to the self-hosted Gitea PyPI registry. No tag required. The pipeline is already validated on the dev channel: `aegis-gitea-mcp-dev` `0.2.0.dev243` published successfully. ## Verify after merge - The Actions run for this push is green (lint, test, publish). - Stable package appears at https://git.hiddenden.cafe/Hiddenden/-/packages/pypi/aegis-gitea-mcp ## Notes - Version stays `0.2.0` (first stable publish, no conflict). Bump `version` in `pyproject.toml` first if you want a different stable number. - Re-running `main` at the same version is a clean no-op: `uv publish --check-url` skips files already present in the registry.

Bartender added 3 commits 2026-06-27 14:14:47 +00:00

ci: publish package on merge to dev/main with separate dev and stable packages ... e5dfba208e

Replace the tag-only publish trigger (no v* tags ever existed, so the
package was never built) with branch-push publishing:

- dev push  -> aegis-gitea-mcp-dev at X.Y.Z.dev<run_number> (always unique)
- main push -> aegis-gitea-mcp at X.Y.Z, a clean no-op via uv --check-url
  if that version is already in the registry

Name + version are patched into pyproject.toml at build time only; the
committed file keeps aegis-gitea-mcp / X.Y.Z. Lint + test gates still run
before publish, and the REGISTRY_TOKEN secret is required (fail-closed).

docs: document dev and stable package channels ... 45641f8e2c

Document the two publish channels (aegis-gitea-mcp from main,
aegis-gitea-mcp-dev from dev), install commands for each, that both share
the aegis_gitea_mcp module so only one installs per environment, and the
merge-driven stable release flow (bump version -> PR into dev -> promote
dev to main; re-pushing main at the same version is a --check-url no-op).

Merge pull request 'ci: fix package publishing + add dev/main packages' (#65) from fix/package-publishing into dev 64611d9c53

Latte merged commit 524cc1773d into main 2026-06-27 14:16:34 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

Compat/Breaking

Breaking change, not backwards compatible

Kind/Bug

Something is not working

Kind/Chore

Maintenance, deps, CI/CD

Kind/Documentation

Documentation changes

Kind/Enhancement

Improve existing functionality

Kind/Feature

New functionality

Kind/Refactor

Code restructuring, no behavior change

Kind/Security

Security-related issue

Priority/Critical

Must be addressed immediately

Priority/High

Important, address soon

Priority/Low

Nice to have

Priority/Medium

Normal priority

Reviewed/Confirmed

Issue has been confirmed

Reviewed/Duplicate

Already tracked elsewhere

Reviewed/Won't Fix

Acknowledged but won't be addressed

Status/Blocked

Blocked by an external dependency

Status/In Progress

Currently being worked on

Status/Need More Info

Needs more information to proceed

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

Bartender (Bartender) Latte (Latte)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Hiddenden/AegisGitea-MCP#66