Skip to content

Vesuvius -> Yellowstone#313

Merged
awisniew207 merged 7 commits intowyatt/datil-testfrom
andrew/yellowstone
Jul 22, 2024
Merged

Vesuvius -> Yellowstone#313
awisniew207 merged 7 commits intowyatt/datil-testfrom
andrew/yellowstone

Conversation

@awisniew207
Copy link
Contributor

  • Chronicle Vesuvius -> Chronicle Yellowstone
  • Renamed files which specified vesuvius
  • Fixed broken links I found when renaming them to Yellowstone
  • Double-checked all links I renamed for functionality
  • Changed chain information to match what we have here

My questions:
./migrations/migrating-to-yellowstone did not exist, changed it to ./migrating-to-yellowstone. Two instances of this, should we make a new folder for it? Current location is docs/connecting-to-a-lit-network.
docs/connecting-to-a-lit-network/testnets.md says 6.1.0 is the earliest version of datil-dev, with the migration to Yellowstone, what would we change it to?

@netlify
Copy link

netlify bot commented Jul 22, 2024

Deploy Preview for lit-dev-docs ready!

Name Link
🔨 Latest commit 681c4aa
🔍 Latest deploy log https://app.netlify.com/sites/lit-dev-docs/deploys/669ecf7510ab320008e1d5e7
😎 Deploy Preview https://deploy-preview-313--lit-dev-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@a1ttech
Copy link
Contributor

a1ttech commented Jul 22, 2024

./migrations/migrating-to-yellowstone did not exist, changed it to ./migrating-to-yellowstone. Two instances of this, should we make a new folder for it? Current location is docs/connecting-to-a-lit-network.

Right now we have this page in the docs which has the URL 'migrating-to-vesuvius' , we should probably update that right?

@a1ttech
Copy link
Contributor

a1ttech commented Jul 22, 2024

Or actually it looks like you already did that. I think you're asking where the link should link to? Because i think we should link to this page: https://developer.litprotocol.com/connecting-to-a-lit-network/migrating-to-vesuvius

@a1ttech
Copy link
Contributor

a1ttech commented Jul 22, 2024

I believe latest would be 6.2.2 (not yet published) but not 100% sure

@Spacesai1or
Copy link

@awisniew207 I'm going to change base branch of this PR to wyatt/datil-test as they both should be merged together and wyatt/datil-test needs the vesuvius -> yellowstone changes as well

@Spacesai1or Spacesai1or changed the base branch from main to wyatt/datil-test July 22, 2024 21:45
@Spacesai1or
Copy link

docs/connecting-to-a-lit-network/testnets.md says 6.1.0 is the earliest version of datil-dev, with the migration to Yellowstone, what would we change it to?

I think it needs to be the latest version of the SDK (the one that introduces yellowstone support)

@Spacesai1or
Copy link

Other than the merge conflicts I made, lgtm

@awisniew207
Copy link
Contributor Author

Datil -> datil-prod
Any 6.1.0/6.2.0 for minimum version updated to 6.2.2 to support Yellowstone
Removed all Vesuvius again
Checked the links again

@awisniew207 awisniew207 merged commit 465abb7 into wyatt/datil-test Jul 22, 2024
@awisniew207 awisniew207 deleted the andrew/yellowstone branch July 22, 2024 22:39
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