-
Notifications
You must be signed in to change notification settings - Fork 83
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
Deploy 2.4.0 #340
Closed
Closed
Deploy 2.4.0 #340
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 9, 2023
Merged
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
This was referenced Nov 9, 2023
Merged
oveddan
changed the base branch from
move-deployment-utils-to-protocol-deployments
to
remove-supply-royalty-deprecation-test
November 9, 2023 23:36
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
from
November 9, 2023 23:36
23722ea
to
9d93657
Compare
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
from
November 9, 2023 23:46
9d93657
to
f3b4b72
Compare
oveddan
force-pushed
the
remove-supply-royalty-deprecation-test
branch
from
November 10, 2023 00:14
4dce800
to
edcd9cc
Compare
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
from
November 10, 2023 00:15
f3b4b72
to
2d71e19
Compare
oveddan
force-pushed
the
remove-supply-royalty-deprecation-test
branch
from
November 10, 2023 01:30
edcd9cc
to
14683d5
Compare
oveddan
changed the base branch from
remove-supply-royalty-deprecation-test
to
move-deployment-utils-to-protocol-deployments
November 10, 2023 01:30
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
2 times, most recently
from
November 10, 2023 01:41
6c59ba3
to
2778576
Compare
This was referenced Nov 13, 2023
Merged
This was referenced Nov 13, 2023
oveddan
force-pushed
the
move-deployment-utils-to-protocol-deployments
branch
2 times, most recently
from
November 14, 2023 20:06
766037e
to
c29433e
Compare
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
from
November 14, 2023 20:10
4776e2f
to
16d11cc
Compare
oveddan
added a commit
that referenced
this pull request
Nov 14, 2023
If we choose to pin protocol-deployments to a specific version of 1155, it imports it via npm and doesnt symlink, thus losing the `test` folder, and we get an error its looking for fixtures in the `test` folder of 1155. This moves all Deployment related code to the `protocol-deployments` package, thus removing that link. See this in action in the downstream PR #340 where we can pin `protocol-deployments` to a specific version of `1155-contracts` - 2.4.0
oveddan
changed the base branch from
move-deployment-utils-to-protocol-deployments
to
main
November 14, 2023 23:59
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
2 times, most recently
from
November 15, 2023 23:01
5612798
to
e907c9b
Compare
oveddan
changed the title
Deploy 2.4.0 to zora-testnet (prerelease)
Deploy 2.4.0 (prerelease)
Nov 16, 2023
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
3 times, most recently
from
November 17, 2023 16:29
d2fb1d2
to
554aa1c
Compare
oveddan
force-pushed
the
deploy-2.4.0-prerelease
branch
from
November 17, 2023 19:04
e2c5e03
to
5845ab3
Compare
iainnash
pushed a commit
that referenced
this pull request
Jan 5, 2024
If we choose to pin protocol-deployments to a specific version of 1155, it imports it via npm and doesnt symlink, thus losing the `test` folder, and we get an error its looking for fixtures in the `test` folder of 1155. This moves all Deployment related code to the `protocol-deployments` package, thus removing that link. See this in action in the downstream PR #340 where we can pin `protocol-deployments` to a specific version of `1155-contracts` - 2.4.0
iainnash
pushed a commit
that referenced
this pull request
Jan 11, 2024
If we choose to pin protocol-deployments to a specific version of 1155, it imports it via npm and doesnt symlink, thus losing the `test` folder, and we get an error its looking for fixtures in the `test` folder of 1155. This moves all Deployment related code to the `protocol-deployments` package, thus removing that link. See this in action in the downstream PR #340 where we can pin `protocol-deployments` to a specific version of `1155-contracts` - 2.4.0
iainnash
pushed a commit
that referenced
this pull request
Jan 11, 2024
If we choose to pin protocol-deployments to a specific version of 1155, it imports it via npm and doesnt symlink, thus losing the `test` folder, and we get an error its looking for fixtures in the `test` folder of 1155. This moves all Deployment related code to the `protocol-deployments` package, thus removing that link. See this in action in the downstream PR #340 where we can pin `protocol-deployments` to a specific version of `1155-contracts` - 2.4.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.