reference.md

# Materize release reference

## Backend: cmd → staging / production tag

| Service | Source (`cmd/`) | Staging tag pattern | Production tag pattern |
|---------|-----------------|---------------------|------------------------|
| REST API | `cmd/rest` | `rest-v*.*.*-staging` | `rest-v*.*.*-production` |
| Peruri batch poll | `cmd/consumer/peruri/batch_poll` | `consumer-peruri-batch-poll-v*.*.*-staging` | `consumer-peruri-batch-poll-v*.*.*-production` |
| Peruri batch generate | `cmd/consumer/peruri/batch_generate` | `consumer-peruri-batch-v*.*.*-staging` | `consumer-peruri-batch-v*.*.*-production` |
| Stamp upload document | `cmd/consumer/stamp/upload_document` | `consumer-stamp-v*.*.*-staging` | `consumer-stamp-v*.*.*-production` |
| Webhook | `cmd/consumer/webhook` | `consumer-webhook-v*.*.*-staging` | `consumer-webhook-v*.*.*-production` |

Drone triggers: `materize-be/.drone.yml` (`refs/tags/…` must match exactly).

---

## Path → binary heuristics

| Paths / signals | Binary | Tag prefix |
|-----------------|--------|------------|
| `cmd/rest`, `router/rest.go`, `config/rest.go`, `internal/.../primary/rest/` | REST | `rest-v` |
| `cmd/consumer/stamp/upload_document`, stamp upload consumer wiring | stamp consumer | `consumer-stamp-v` |
| `cmd/consumer/peruri/batch_poll` | peruri batch poll | `consumer-peruri-batch-poll-v` |
| `cmd/consumer/peruri/batch_generate` | peruri batch generate | `consumer-peruri-batch-v` |
| `cmd/consumer/webhook` | webhook | `consumer-webhook-v` |
| `cmd/consumer/product` | (no Drone pipeline in repo — do not tag unless pipeline exists) | — |

### Shared `internal/` (decision tree)

1. Change only in one `cmd/<service>/` → tag that binary only.
2. Change in `internal/adapters/framework/primary/rest/` or `router/rest.go` → usually **REST** only.
3. Change in `internal/adapters/core/stamp/` (balance, stamp-multi, upload, debit/refund) → often **REST + consumer-stamp** (REST accepts API; consumer runs upload/PDF pipeline). Match recent changelog Notes (“Deploy: REST and consumer stamp”).
4. Change in Peruri batch core used by poll consumer → **consumer-peruri-batch-poll** (and REST only if REST handlers changed).
5. When unsure: list which `main.go` binaries link the changed packages; tag every binary that must ship the fix.

---

## Frontend tags

| Environment | Pattern | Example |
|-------------|---------|---------|
| Staging | `fe-v*.*.*-staging` | `fe-v0.19.0-staging` |
| Production | `fe-v*.*.*-production` | `fe-v0.19.0-production` |

Latest tag:

```bash
git tag -l 'fe-v*-staging' --sort=-v:refname | head -1
```

SemVer (from `materize-fe/CHANGELOG.md`): PATCH = bug/style; MINOR = new non-breaking feature; MAJOR = breaking UX/API contract.

---

## Example release shapes

**REST only** — digital certificate API in REST handlers:

- Tags: `rest-v1.12.4-staging`
- Changelog title: `## [1.12.4] — REST only — YYYY-MM-DD`

**REST + consumer stamp** — shared stamp balance / stamp-multi:

- Tags: `rest-v1.12.7-staging`, `consumer-stamp-v0.1.4.6-staging`
- Notes: deploy `cmd/rest` and `cmd/consumer/stamp/upload_document`

**Consumer only** — peruri batch poll:

- Tags: `consumer-peruri-batch-poll-v0.0.4-staging`
- Changelog may use consumer version in header (`## [0.0.3] — Consumer only …`)

**FE minor** — new portal feature:

- Tag: `fe-v0.19.0-staging`
- Changelog: `## [0.19.0] — YYYY-MM-DD`

---

## Last tag commands (BE)

```bash
git tag -l 'rest-v*-staging' --sort=-v:refname | head -1
git tag -l 'consumer-stamp-v*-staging' --sort=-v:refname | head -1
git tag -l 'consumer-peruri-batch-poll-v*-staging' --sort=-v:refname | head -1
git tag -l 'consumer-peruri-batch-v*-staging' --sort=-v:refname | head -1
git tag -l 'consumer-webhook-v*-staging' --sort=-v:refname | head -1
```