Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

atom-linter@4.2.0 untested ⚠️ #4

Merged
merged 1 commit into from
Dec 30, 2015
Merged

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello 👋

⚠️⚠️⚠️

atom-linter just published its new version 4.2.0, which is covered by your current version range. No automated tests are configured for this project.

This means it’s now unclear whether your software still works. Manually check if that’s still the case
and close this pull request – if it broke, use this branch to work on adaptions and fixes.

Do you think getting a pull request for every single new version of your dependencies is too noisy? Configure continuous integration and you will only receive them when tests fail. 

Happy fixing and merging 🌴


The new version differs by 7 commits .

  • 5ed7924 :arrow_up: Bump version to 4.2.0
  • 662544a Merge pull request #86 from AtomLinter/steelbrain/use-consistent-path
  • 970370f :arrow_up: Bump version to 1.0.1
  • bb8e568 :memo: Document change in CHANGELOG
  • 42b68ca :new: Use consistent-path
  • 02a08bd Merge pull request #79 from AtomLinter/update-readme
  • 662cff0 Document colStart parameter to rangeFromLineNumber

See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

xpol added a commit that referenced this pull request Dec 30, 2015
@xpol xpol merged commit 70a776d into master Dec 30, 2015
@steelbrain steelbrain deleted the greenkeeper-atom-linter-4.2.0 branch December 30, 2015 13:30
@Arcanemagus
Copy link
Member

Mind pushing out a release including this? I want to try to get most linter-* plugins updated to include this so hopefully we can bypass atom/atom#9775.

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

Successfully merging this pull request may close these issues.

None yet

3 participants