Skip to content

Conversation

@Hunterness
Copy link
Contributor

@Hunterness Hunterness commented May 20, 2025

Copy link
Contributor

@Lojjs Lojjs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You also need a header which say which version it was changed in, like this
:page-role: changed-2025.06

(Cutoff for 2025.05 has been right??)

@Hunterness
Copy link
Contributor Author

(Cutoff for 2025.05 has been right??)

I think so? the 04 version tag was from April 17th and we did have a cutoff now in May which should be the 05 one

@Lojjs Lojjs added the 2025.06 label May 20, 2025
@renetapopova renetapopova force-pushed the dev-51N31-item-to-feat branch from 6ccbc5a to 47631fd Compare June 5, 2025 15:12
@renetapopova renetapopova merged commit e181f58 into neo4j:dev Jun 5, 2025
4 checks passed
@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-status-codes-328.surge.sh

Updated pages:

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants