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

V6 API #433

Merged
merged 40 commits into from
Apr 11, 2018
Merged

V6 API #433

merged 40 commits into from
Apr 11, 2018

Conversation

MarshallOfSound
Copy link
Member

@MarshallOfSound MarshallOfSound commented Feb 19, 2018

  • I have read the contribution documentation for this project.
  • I agree to follow the code of conduct that this project follows, as appropriate.
  • The changes are appropriately documented (if applicable).
  • The changes have sufficient test coverage (if applicable).
  • The testsuite passes successfully on my local machine (if applicable).

This is still WIP but I thought I'd put a PR up so people can easily see the diff 😄

@MarshallOfSound MarshallOfSound changed the base branch from master to v6 February 19, 2018 05:44
@MarshallOfSound
Copy link
Member Author

Git's diff isn't smart enough to realize but not much code has changed here, lot's of this is just transposition

.travis.yml Outdated
install:
- npm install
- npm update
- npm i -g bolt
Copy link
Member

Choose a reason for hiding this comment

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

Does it have to be installed globally?

Copy link
Member

Choose a reason for hiding this comment

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

Never mind, yes, it does.

@@ -0,0 +1 @@
8.9.1
Copy link
Member

Choose a reason for hiding this comment

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

Is this necessary to be committed to the repo?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not required, but helpful for most macOS / *nix users who use nvm (it will auto-select the node version).

Copy link
Member

Choose a reason for hiding this comment

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

It's kind of odd that it's Node 8 when the minimum version is Node 6.

Copy link
Member Author

Choose a reason for hiding this comment

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

Recommend Dev version, not version required for using

fakeMake('darwin').reduce((accum, val) => accum.concat(val.artifacts), []).sort()
);
expect(darwinArgs.packageJSON).to.deep.equal({ state: 1 });
expect(darwinArgs.authToken).to.equal(undefined);
expect(darwinArgs.tag).to.equal(null);
expect(darwinArgs.tag).to.equal('1.0.0');
Copy link
Member

Choose a reason for hiding this comment

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

@MarshallOfSound I'm not sure about this change I made to get the publisher tests working, let me know if this is incorrect.

@malept
Copy link
Member

malept commented Apr 4, 2018

I think boltpkg/bolt#154 blocks the Windows tests from passing.

@malept
Copy link
Member

malept commented Apr 8, 2018

That bolt PR has been merged, waiting for it to be in a new release ⏳

MarshallOfSound and others added 7 commits April 9, 2018 00:57
* Allow absolute paths to custom modules
* Update to new @electron-forge/ scope
tabtab is rather buggy and the alternative, commander-completion, needs
a custom completion script to be written and maintained.
@MarshallOfSound
Copy link
Member Author

MarshallOfSound commented Apr 8, 2018

When we merge this I'm going to release all the modules on npm as 6.0.0-beta.1 with the beta tag. Just so people can start picking it up but we're not marking it as flawless. In a giant refactor like this I've undoubtedly caused a few new issues 😄

Future releases will all have the same version number to make tracking easier. I.e. Changing something in one module will result in new versions of all modules. We will only officially support the case where you all your forge dependencies are the same version.

@MarshallOfSound MarshallOfSound changed the title [WIP] V6 API V6 API Apr 11, 2018
@MarshallOfSound
Copy link
Member Author

As soon as this goes green I'm gonna merge it, will do add docs over time but want to get at least a beta out there so I can start using it 😀

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.

None yet

3 participants