Skip to content

Pass GitHub release timestamp to RecordRelease API#63

Merged
gontzess merged 1 commit intomainfrom
gontzess/record-release-timestamp
Mar 20, 2026
Merged

Pass GitHub release timestamp to RecordRelease API#63
gontzess merged 1 commit intomainfrom
gontzess/record-release-timestamp

Conversation

@gontzess
Copy link
Copy Markdown
Contributor

Why

RecordRelease currently uses server time.Now() as releasedAt, which is ~35 minutes after the actual GitHub release creation. This causes timestamp drift between what dist.conductorone.com shows and what the registry records.

What this changes

  • Fetches created_at from the GitHub release API in the release workflow
  • Passes it to record-release via new -released-at flag
  • The registry API accepts this as an optional released_at field (falls back to server time if not provided)

Depends on: ductone/connector-registry-api#61

Fetch the release created_at from the GitHub API and pass it to
record-release via -released-at flag. The registry API uses this
as the release's releasedAt instead of server time, matching what
dist.conductorone.com shows.

Depends on: ductone/connector-registry-api#61 (adds released_at
field to RecordReleaseRequest proto)
@gontzess gontzess marked this pull request as ready for review March 20, 2026 00:20
@gontzess gontzess merged commit 1f7a75e into main Mar 20, 2026
1 check passed
@gontzess gontzess deleted the gontzess/record-release-timestamp branch March 20, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants