Skip to content

Avoid building outdated branches #462

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Conversation

stefano-ottolenghi
Copy link
Contributor

Currently drivers supported versions are 4.4 and 5.x. Is there any reason why we should keep building old versions @recrwplay ? As far as I know, they will stay online even if we stop building them explicitly, as we don't delete old versions.

@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-drivers-462.surge.sh

@recrwplay
Copy link
Contributor

It's a good question. Versions back to 4.0 are listed as compatible with 4.4 LTS on https://neo4j.com/developer/kb/neo4j-supported-versions/ but I don't now whether that in itself creates a requirement for the docs for these versions to be published alongside current and supported versions.

I don't think it would be a problem if they were removed from the version selector but still available (which they would be). Anyone already using an older version who wants to use the docs could probably get to the correct URL. This change would remove 4.2 and 4.3 from the version selector from each driver, and earlier versions would be available as they are now (ie published as the single 'Driver manual').

Docs for those earlier versions can be accessed from the links in https://neo4j.com/docs/reference/docs-archive/#_neo4j_drivers

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.

3 participants