Is the goreleaser/goreleaser-action GitHub Action still maintained?
not-checked — observed 2026-09-07
As of 2026-09-07, the GitHub Action github.com/goreleaser/goreleaser-action is recorded not-checked: the repository was not observed on this date (an absent reading, not a state). 2 dated observation(s) on record since 2026-08-02; 1020 stars and 100 forks read 2026-08-02.
github.com/goreleaser/goreleaser-action is recorded as not-checked in the lastseen.dev component-maintenance dataset as of 2026-09-07. Definition: the repository was not observed on this date (an absent reading, not a state). Adoption at the latest read: 1020 stars, 100 forks (read 2026-08-02). The page carries 2 dated observations from 2026-08-02 onward. The recorded state changed 1 time(s) across the series. Method: read from the public GitHub repository metadata and star/fork counts (authoritative). This is a dated factual observation series about one GitHub Action, not advice about any named party.
API: this register also serves a free JSON API — see /api/v1/docs. (Per-entity GET/POST covers MCP servers and npm packages; this surface is page-only for now.)
- State (latest)
- not-checked — the repository was not observed on this date (an absent reading, not a state)
- Last public activity
- — (not recorded in the series)
- Dated observations
- 2, from 2026-08-02 to 2026-09-07
- State changes
- 1 across the series
- Adoption (latest read 2026-08-02)
- 1020 stars · 100 forks
- Method
- GitHub repository metadata + star/fork counts (authoritative)
- Source / evidence
- github.com/goreleaser/goreleaser-action
- Observed as of
- 2026-09-07
- Registry
- GitHub Actions
Interval-censoring. Observation window from 2026-08-02 to 2026-09-07, with 2 dated observations. A state transition inside an unobserved span is dated to that interval, not to a single day. The star and fork counts are the values read at the latest successful adoption observation (2026-08-02). Absence of an observation on a date is recorded as not observed, never as a state.
A dated observation series, not advice. Data under CC-BY-4.0. Check every dependency in one place: check your whole organization.
Dated observation series
| observation date | state | last public activity |
|---|---|---|
| 2026-08-02 | alive | 2026-08-01 |
| 2026-09-07 | not-checked | — |
State-mutation history
The recorded state changed 1 time(s) across the series. Each change is dated to the observation on which the new state was first read:
- alive → not-checked observed 2026-09-07
When was it last active?
The last public activity read for this repository was dated not recorded in the series. State not-checked reflects the repository was not observed on this date (an absent reading, not a state).
What is its recorded state?
State not-checked is derived from the public GitHub repository metadata read on each observation date: the repository was not observed on this date (an absent reading, not a state).
What does that mean for projects using it?
At the latest adoption read (2026-08-02) the repository showed 1020 stars and 100 forks — the adoption signal that qualifies this Action for a page. A workflow that pins this Action by a tag or SHA continues to resolve to its last published ref; a floating major-version ref has no newer release to resolve to. This is a dated observation, not advice about any named party.
What is the observation record?
The record is the dated series above: 2 observations from 2026-08-02 to 2026-09-07, each with a state and a last-activity date, plus 1 state change(s). A dispute re-reads the public GitHub metadata and issues a dated correction on this page.