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: merge 0.14.0-beta1 #86

Merged
merged 1,042 commits into from
Apr 1, 2021
Merged

feat: merge 0.14.0-beta1 #86

merged 1,042 commits into from
Apr 1, 2021

Conversation

brew0722
Copy link
Contributor

@brew0722 brew0722 commented Mar 19, 2021

Closes: #79

Description

This PR merges CosmWasm/cosmwasm:v0.14.0-beta1 and migrates contracts/token-tester and contracts/collection-tester.

contracts real running test are going to be done after lbm-sdk and wasmvm also merged to v0.14.0-beta1.
After merging this commit, I will make our version and write the CHANGELOG.

Motivation and context

How has this been tested?

Cargo test is passed.
The integration test proceeds after wasmvm and wasmd merge.

Checklist:

  • I followed the contributing guidelines.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@brew0722
Copy link
Contributor Author

brew0722 commented Mar 24, 2021

I think github action is used in v0.12.0 and later, and should be enabled in our repository. How about it?

Of course I think it's good.
However, as far as I know has not yet been decieded within the dev2 dept. Because of the usage fee and another things.

@whylee259
Copy link
Contributor

I think github action is used in v0.12.0 and later, and should be enabled in our repository. How about it ?

Let's do it on another issue.

@whylee259 whylee259 mentioned this pull request Mar 24, 2021
2 tasks
@brew0722 brew0722 changed the title (WIP) feat: merge 0.14.0-beta1 feat: merge 0.14.0-beta1 Mar 31, 2021
@brew0722 brew0722 changed the title feat: merge 0.14.0-beta1 (WIP) feat: merge 0.14.0-beta1 Mar 31, 2021
@brew0722
Copy link
Contributor Author

It will be rewritten based on #98.

@brew0722 brew0722 linked an issue Mar 31, 2021 that may be closed by this pull request
Jiyong Ha added 2 commits March 31, 2021 13:37
* tag 'v0.14.0-beta1+contracts1': (904 commits)
  Add reference to the other InitCallback
  Fix reflect incompatiblity
  Format shell script
  Remove hopelessly outdated building instructions
  Revert "Add dev branch for testing"
  Simplify path
  Use check_contract.sh helper in CI
  Add `check_contract.sh` helper
  Run `check_contract` in its own container
  Revert "Change CI build and release image"
  Revert "Add ghr (and go) to build and deploy stage"
  Add dev branch for testing
  Add ghr (and go) to build and deploy stage
  Change CI build and release image
  Format clean scripts
  Rename workspace clean
  Add clean_contracts script
  Make check_contracts work with clean repo
  Set version: 0.14.0-beta1
  Fix benchmarking
  ...
@brew0722 brew0722 changed the title (WIP) feat: merge 0.14.0-beta1 feat: merge 0.14.0-beta1 Mar 31, 2021
@brew0722
Copy link
Contributor Author

brew0722 commented Mar 31, 2021

I'm done.
12.0 commit was removed from the list of commits.(1359 -> 1037)
And removed fix commit by git bug after squash merge.

PTAL @shiki-tak @whylee259 @loloicci

Copy link
Contributor

@loloicci loloicci left a comment

Choose a reason for hiding this comment

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

Some PR are reverted in this PR. Are these merged again after this PR?

packages/vm/src/testing/mod.rs Show resolved Hide resolved
packages/vm/src/testing/mock.rs Show resolved Hide resolved
Copy link
Contributor

@loloicci loloicci left a comment

Choose a reason for hiding this comment

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

about commits' title:

fix: revert pull request xx (ab0da46, 4b99966): revert -> patch or apply? (revert sounds like cansel in git)
refactor: migrate testing to 0.14.0-beta1 (503707d): looks doing more than refactor. It including fix of our PRs for 0.14.0.

@@ -1,26 +1,30 @@
# See https://doc.mergify.io/configuration.html

pull_request_rules:
- name: automerge to master with label automerge
- name: automerge to main with label automerge
Copy link
Contributor

Choose a reason for hiding this comment

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

Will our repository also migrate its name from master to main?

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, let's do it ASAP.
I have made it.

@brew0722
Copy link
Contributor Author

brew0722 commented Apr 1, 2021

about commits' title:

fix: revert pull request xx (ab0da46, 4b99966): revert -> patch or apply? (revert sounds like cansel in git)
refactor: migrate testing to 0.14.0-beta1 (503707d): looks doing more than refactor. It including fix of our PRs for 0.14.0.

  • 'revert' -> 'repatch' modified that. if is it unsounds, please suggestion again
  • your suggestion is 'migrate ...' -> 'refactor ...' right? The collection-tester, token-tester, and testing were modified for 0.14.0 migration rather than a structure or interface changes, so they were expressed as 'migrate'.
  • 'mod result;' patch line rebased to 'fix: repatch pull request feat: implement vm::testing::Contract which represents a contract in integration tests #87'

@loloicci
Copy link
Contributor

loloicci commented Apr 1, 2021

your suggestion is 'migrate ...' -> 'refactor ...' right?

No, my suggestion is 'refactor' -> 'fix'.
My opinion is "this commit changes the behavior of some test, so it is exceeded the refactoring".

@brew0722
Copy link
Contributor Author

brew0722 commented Apr 1, 2021

your suggestion is 'migrate ...' -> 'refactor ...' right?

No, my suggestion is 'refactor' -> 'fix'.
My opinion is "this commit changes the behavior of some test, so it is exceeded the refactoring".

I understand, thks good suggestion

@brew0722 brew0722 merged commit 65c2374 into Finschia:develop Apr 1, 2021
@brew0722 brew0722 deleted the merge_0_14_0_beta1 branch April 1, 2021 09:30
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.

Adjustment according to migration PR merge policy change migrate 0.14.0
8 participants