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

Upgrade debug version of eslint-module-utils #844

Merged
merged 1 commit into from Jun 2, 2017

Conversation

popomore
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented May 24, 2017

Coverage Status

Coverage remained the same at 95.059% when pulling d7245a8 on popomore:upgrade-debug into b79e083 on benmosher:master.

@popomore
Copy link
Contributor Author

Appveyor failed, but not caused by this PR, it seems coveralls do some wrong things.

@popomore
Copy link
Contributor Author

cc @benmosher

@popomore
Copy link
Contributor Author

Ping @benmosher

@benmosher benmosher merged commit dfbe0e7 into import-js:master Jun 2, 2017
@popomore popomore deleted the upgrade-debug branch June 4, 2017 14:46
@popomore
Copy link
Contributor Author

popomore commented Jun 4, 2017

@benmosher When will release next version?

sompylasar added a commit to sompylasar/eslint-plugin-import that referenced this pull request Jun 4, 2017
…h_in_parser_options

* commit '3c46d308ccb462a52554257c49c374045d1a6cf7':
  rollback utils dependency to 2.0.0
  add yank note to utils change log
  add yanking note to root change log
  Upgrade debug version of eslint-module-utils (import-js#844)
  remove obsolete dad joke
  update utils changelog
  bump eslint-module-utils to v2.1.0
  bump v2.4.0
  fix typos, enforce type of array of strings in allow option
  update CHANGELOG.md
  eslint-module-utils: filePath in parserOptions (import-js#840)
  write doc, add two more tests
  add allow glob for rule no-unassigned-import, fix import-js#671

# Conflicts:
#	utils/CHANGELOG.md
@benmosher
Copy link
Member

not sure, have to investigate #863 first 😩

@popomore
Copy link
Contributor Author

popomore commented Jun 8, 2017

@benmosher bad news, hope this issue could be resolved soon, thx for doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants