Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Specify compatibility with node in release notes, with a dedicated nightly job #742

Open
smelc opened this issue Apr 26, 2024 · 9 comments
Open

Specify compatibility with node in release notes, with a dedicated nightly job #742

smelc opened this issue Apr 26, 2024 · 9 comments
Assignees
@smelc

Comments

@smelc
Copy link
Contributor

smelc commented Apr 26, 2024

As agreed on Slack, we want to update our release notes with a compatibility section, that indicates when a node version is known to be compatible with a cardano-cli version. We will find this information by parsing the node's cabal file, and looking the version of cardano-cli specified there. Then we'll lookup the corresponding cli release, and state that it is compatible with this node version.

We want this to be automatic, and performed by a nightly GHA job. We'll use gh and this PATCH endpoint.
@smelc smelc self-assigned this Apr 26, 2024
@carbolymer
Copy link
Contributor

Tangentially related discussion: IntersectMBO/cardano-node#5795 (comment)

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label May 27, 2024
@smelc smelc removed the Stale label May 27, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Jun 27, 2024
@smelc
Copy link
Contributor Author

smelc commented Jun 27, 2024

I have started this a few weeks ago, but it's more work than I had anticipated. It's stopped right now.

@smelc smelc removed the Stale label Jun 27, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Jul 28, 2024
@carbolymer carbolymer removed the Stale label Jul 29, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Aug 29, 2024
@smelc smelc removed the Stale label Aug 29, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Sep 29, 2024
@smelc smelc removed the Stale label Sep 30, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Oct 31, 2024
@smelc smelc removed the Stale label Oct 31, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 1, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.

@github-actions github-actions bot added the Stale label Dec 1, 2024
@smelc smelc removed the Stale label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smelc smelc

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@carbolymer @smelc