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.

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

Node-ng 8.10.1, dbsync 13.2.0.2, mithril-ng unstable, private chain stop #22

Merged
merged 12 commits into from
Apr 29, 2024

Conversation

johnalotoski
Copy link
Collaborator

@johnalotoski johnalotoski commented Apr 22, 2024

Overview:

Sets cardano-node pre (-ng) to 8.10.1, dbsync to 13.2.0.2, mithril pre (-ng) to unstable, iohk-nix and iohk-nix-ng to include new CF relays, adds a public TLS dbsync user connection option, stops private chain cluster. See cardano-parts PR#39 for additional details on upstream improvements.

Details:

  • Bumps cardano-db-sync 13.2.0.1 -> 13.2.0.2
  • Bumps cardano-node pre (-ng) 8.10.0 -> 8.10.1
  • Bumps mithril pre (-ng) 2412.0 -> unstable
  • Bumps iohk-nix, iohk-nix-ng for CF bootstrap relays
  • Adds a public TLS dbsync user conn option
  • Adds template apply-bootstrap recipe
  • Adds template aws specific recipes for machine control: aws-ec2-{id,start,status,stop}
  • Updates template python script lib for release or pre-release 8.10.x version compatibility
  • Updates book with PeerSharing non-block-producer config vs block producer config warning note
  • Stops private chain cluster for now until Voltaire is ready to resume testing

@johnalotoski johnalotoski force-pushed the next-2024-04-19 branch 3 times, most recently from 37d9bfe to c486153 Compare April 23, 2024 14:49
@johnalotoski johnalotoski changed the title Next 2024 04 19 Node-ng 8.10.1, dbsync 13.2.0.2, mithril-ng unstable, private chain stop Apr 29, 2024
@johnalotoski johnalotoski merged commit abcd5c3 into main Apr 29, 2024
2 checks passed
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.

1 participant