Skip to content

docs: install the current GraphForge release without version pins #374

Description

@DecisionNerd

Problem

Public install guidance hard-codes the most recent package version, so it becomes stale with every release.

Acceptance criteria

  • Root README, docs site, binding READMEs, use cases, and examples install GraphForge by package name.
  • Installation copy no longer instructs readers to pin the current release.
  • README and docs home show live PyPI and npm version badges.
  • A regression test rejects pinned Python install guidance.
  • Documentation build passes.

Activity

  1. coderabbitai commented on Aug 3, 2026

    @coderabbitai
    🔗 Related PRs

    #297 - docs(release): require one shared product version [merged]
    #308 - fix(release): align crate path+version pins to 0.5.1 [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions