Skip to content

chore(main): release 0.1.0#23

Closed
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--gitpulse
Closed

chore(main): release 0.1.0#23
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main--components--gitpulse

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 2, 2026

🤖 I have created a release beep boop

0.1.0 (2026-05-02)

Features

  • Open PR detail in a right-side drawer with scroll preserve (#25) (0a31f0f)
  • Redesign PR detail page (port from gitsky) (#24) (32a2f7d)

Bug Fixes

  • populate first-release editions and simplify URL (#22) (762cd86)

This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--gitpulse branch from 19052b1 to 056c398 Compare May 2, 2026 14:03
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 2, 2026

Greptile Summary

This is an automated release PR generated by Release Please, updating CHANGELOG.md to document the 0.1.0 release. The changelog entry lists two new features (PR detail drawer, redesigned PR detail page) and one bug fix. Previously flagged issues (duplicate 0.1.0 section and self-referential compare URL) remain open on this PR.

Confidence Score: 4/5

Documentation-only PR with pre-existing changelog issues already flagged; no code changes introduced.

The only changed file is CHANGELOG.md. The duplicate version section (a P1 concern already raised in prior threads) and the self-referential compare URL are known issues with this PR, but they do not affect runtime behavior. No new issues were found beyond those already flagged.

CHANGELOG.md — duplicate v0.1.0 section should be resolved before merging.

Important Files Changed

Filename Overview
CHANGELOG.md Release Please–generated changelog entry for v0.1.0; contains a duplicate version section (lines 3 and 16 both define 0.1.0) and a self-referential compare URL, both flagged in prior review threads.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Feature/fix merged to main] --> B[Release Please GitHub Action]
    B --> C{New releasable commits?}
    C -- Yes --> D[Open/update release PR]
    D --> E[Update CHANGELOG.md]
    D --> F[Bump version in manifests]
    E --> G{PR merged?}
    F --> G
    G -- Yes --> H[Release Please tags release]
    H --> I[GitHub Release created]
    C -- No --> J[No action]
Loading

Reviews (3): Last reviewed commit: "chore(main): release 0.1.0" | Re-trigger Greptile

Comment thread CHANGELOG.md
Comment thread CHANGELOG.md
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--gitpulse branch from 056c398 to 6d9a82b Compare May 2, 2026 21:20
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--gitpulse branch from 6d9a82b to c400080 Compare May 2, 2026 23:08
@znat znat closed this May 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant