Skip to content

Use master of js-sdk when running CI on master #29596

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

Closed
wants to merge 1 commit into from

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Mar 26, 2025

We previously checked out develop js-sdk even when building / testing mster. This would have worked usually, except when we have non-backwards compat changes on the js-sdk which we sometimes do with unstable interfaces (like sliding sync).

This changes to use the master branch.

Checklist

  • Tests written for new code (and old code if feasible).
  • New or updated public/exported symbols have accurate TSDoc documentation.
  • Linter and other CI checks pass.
  • I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

We previously checked out develop js-sdk even when building / testing
mster. This would have worked usually, except when we have non-backwards
compat changes on the js-sdk which we sometimes do with unstable
interfaces (like sliding sync).

This changes to use the master branch.
Copy link
Member

@t3chguy t3chguy left a comment

Choose a reason for hiding this comment

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

What about staging? Wouldn't the existing branch matching work here? Feels like something fetchdep should just handle in the branch matching IMO

@dbkr
Copy link
Member Author

dbkr commented Mar 27, 2025

True, looks like we do have env vars that fetchdep can look at directly: have done that in a separate PR: #29601

@dbkr
Copy link
Member Author

dbkr commented Mar 27, 2025

We went with #29601

@dbkr dbkr closed this Mar 27, 2025
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.

2 participants