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

feat: update Stride IGP to our own, temporarily whitelist our Stride deployment #4748

Merged
merged 3 commits into from
Oct 24, 2024

Conversation

tkporter
Copy link
Collaborator

@tkporter tkporter commented Oct 24, 2024

Description

  • We have an IGP on Stride now. We expect not to fully index this till at least Friday - so for now we just whitelist the messages we care about.

Drive-by changes

Related issues

Backward compatibility

Testing

Copy link

changeset-bot bot commented Oct 24, 2024

⚠️ No Changeset found

Latest commit: 39ceb7e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>
Copy link

codecov bot commented Oct 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.81%. Comparing base (3474a84) to head (39ceb7e).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4748   +/-   ##
=======================================
  Coverage   73.81%   73.81%           
=======================================
  Files         101      101           
  Lines        1455     1455           
  Branches      191      191           
=======================================
  Hits         1074     1074           
  Misses        360      360           
  Partials       21       21           
Components Coverage Δ
core 84.61% <ø> (ø)
hooks 75.71% <ø> (ø)
isms 77.58% <ø> (ø)
token 88.13% <ø> (ø)
middlewares 77.39% <ø> (ø)

@daniel-savu daniel-savu added this pull request to the merge queue Oct 24, 2024
Merged via the queue into main with commit 89c60ab Oct 24, 2024
37 of 38 checks passed
@daniel-savu daniel-savu deleted the trevor/update-stride-relayer branch October 24, 2024 16:24
tiendn pushed a commit to tiendn/hyperlane-monorepo that referenced this pull request Oct 25, 2024
…deployment (hyperlane-xyz#4748)

### Description

- We have an IGP on Stride now. We expect not to fully index this till
at least Friday - so for now we just whitelist the messages we care
about.

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>
tiendn pushed a commit to tiendn/hyperlane-monorepo that referenced this pull request Oct 25, 2024
…deployment (hyperlane-xyz#4748)

### Description

- We have an IGP on Stride now. We expect not to fully index this till
at least Friday - so for now we just whitelist the messages we care
about.

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>
tiendn pushed a commit to tiendn/hyperlane-monorepo that referenced this pull request Oct 25, 2024
…deployment (hyperlane-xyz#4748)

### Description

- We have an IGP on Stride now. We expect not to fully index this till
at least Friday - so for now we just whitelist the messages we care
about.

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>
tiendn pushed a commit to tiendn/hyperlane-monorepo that referenced this pull request Oct 25, 2024
…deployment (hyperlane-xyz#4748)

### Description

- We have an IGP on Stride now. We expect not to fully index this till
at least Friday - so for now we just whitelist the messages we care
about.

### Drive-by changes

<!--
Are there any minor or drive-by changes also included?
-->

### Related issues

<!--
- Fixes #[issue number here]
-->

### Backward compatibility

<!--
Are these changes backward compatible? Are there any infrastructure
implications, e.g. changes that would prohibit deploying older commits
using this infra tooling?

Yes/No
-->

### Testing

<!--
What kind of testing have these changes undergone?

None/Manual/Unit Tests
-->

---------

Co-authored-by: Daniel Savu <23065004+daniel-savu@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants