Skip to content

Conversation

@43081j
Copy link
Member

@43081j 43081j commented Jul 12, 2025

Basically runs CI against various peers to ensure we're still
compatible.

@pi0 let me know if this makes sense. if you know a better way, i'm all ears. this is what i was talking about in #640.

we could also add every peer with @latest to get ahead on if a new major is published that we're not compatible with

Basically runs CI against various peers to ensure we're still
compatible.
@43081j 43081j requested a review from pi0 as a code owner July 12, 2025 18:57
@pi0
Copy link
Member

pi0 commented Jul 14, 2025

Intreating approach. What do you think if we instead add a script to check latest version of peer deeps (test next major in CI), it is a little hard to keep testing all older versions.

@43081j
Copy link
Member Author

43081j commented Jul 14, 2025

similar to this but using latest of every peer?

we could probably assume older ones work since we must've tested them in the past. so maybe it is more useful testing against the latest ones

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