Skip to content

Deploy kovan-ovm-futures v0.4.0 (Alpha) #1487

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

Merged
merged 17 commits into from
Aug 31, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion index.js
Original file line number Diff line number Diff line change
Expand Up @@ -454,7 +454,7 @@ const getFuturesMarkets = ({
deploymentPath,
} = {}) => {
if (!deploymentPath && (!path || !fs)) {
return data[getFolderNameForNetwork({ network, useOvm })].rewards;
return data[getFolderNameForNetwork({ network, useOvm })].futuresMarkets;
}

const pathToFuturesMarketsList = deploymentPath
Expand Down
680 changes: 300 additions & 380 deletions publish/deployed/kovan-ovm-futures/deployment.json

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion publish/deployed/local-ovm/.gitignore
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# these files are irrelevant outside of a single developer's machine,
# so no need to persist them in source control
deployment.json
Copy link
Contributor

Choose a reason for hiding this comment

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

I am not clear on what this fixes, since you aren't pushing local-ovm/deployment.json. In general isn't it sensible that updated versions of this aren't committed? Or are we just relying on developers to remember not to commit it?

Copy link
Contributor Author

@liamzebedee liamzebedee Aug 31, 2021

Choose a reason for hiding this comment

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

Sorry - just figured out that there was a better way of doing this. In #1356 I merged in the local-ovm support so that we could develop locally quickly with the futures-keepers. Turns out that NPM will ignore downloading any files specified by .gitignore - and since we need the deployment.json in a local-ovm development context to fetch local contracts, I tried to include it. Just made a change (and tested it) which overrides the gitignore using npmignore - which will allow us to achieve the above.

owner-actions.json
owner-actions.json
1 change: 1 addition & 0 deletions publish/deployed/local-ovm/.npmignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
!deployment.json
15 changes: 8 additions & 7 deletions publish/releases.json
Original file line number Diff line number Diff line change
Expand Up @@ -254,8 +254,8 @@
},
"sources": [
"Exchanger",
"Synthetix",
"FuturesMarketManager",
"Synthetix",
"SystemSettings"
],
"sips": [80]
Expand All @@ -269,16 +269,17 @@
"ovm": true,
"sources": [
"Exchanger",
"Synthetix",
"ProxyFuturesMarketBTC",
"FuturesMarketBTC",
"ProxyFuturesMarketETH",
"FuturesMarketData",
"FuturesMarketETH",
"ProxyFuturesMarketLINK",
"FuturesMarketLINK",
"ProxyFuturesMarketManager",
"FuturesMarketManager",
"FuturesMarketData",
"FuturesMarketSettings",
"ProxyFuturesMarketBTC",
"ProxyFuturesMarketETH",
"ProxyFuturesMarketLINK",
"ProxyFuturesMarketManager",
"Synthetix",
"SystemSettings"
],
"sips": [80]
Expand Down