Skip to content

Move from irc 0.5.2 to irc-upd 0.6.1 #258

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 1 commit into from
Jul 1, 2017

Conversation

Throne3d
Copy link
Collaborator

@Throne3d Throne3d commented Jul 1, 2017

The irc module does not appear to be very actively maintained, and has quite a few issues causing issues in this project itself.

This fork, maintained by me, has a few fixes to some major issues already.

Changelogs:

Should fix #199, #200, as well as some issues not previously noted (crash if unbanning a user who is not banned, crash in circumstances with a poor internet connection).

It may also allow us to remove our workaround for the quit and nick events having all channels in the associated array.

As far as I can tell this breaks no tests (and in fact I added a few to the irc-upd package, since it seems to be lacking) and should (if you trust it to be better maintained than the current one) be a good improvement to the project.

The irc module does not appear to be very actively maintained, and has
quite a few issues causing issues in this project itself.

This fork, maintained by me, has a few fixes to some major issues
already.

Changelogs:

- v0.6.0 - https://github.com/Throne3d/node-irc/releases/tag/v0.6.0
- v0.6.1 - https://github.com/Throne3d/node-irc/releases/tag/v0.6.1

Should fix reactiflux#199, reactiflux#200, as well as some issues not previously noted
(crash if unbanning a user who is not banned, crash in circumstances
with a poor internet connection).

It may also allow us to remove our workaround for the quit and nick
events having all channels in the associated array.
@Throne3d Throne3d self-assigned this Jul 1, 2017
@coveralls
Copy link

coveralls commented Jul 1, 2017

Coverage Status

Coverage remained the same at 98.456% when pulling c0d443d on Throne3d:upgrade/migrate-to-irc-upd into 80c3752 on reactiflux:master.

@ekmartin
Copy link
Member

ekmartin commented Jul 1, 2017

Good idea!

@ekmartin ekmartin merged commit 67ac5f1 into reactiflux:master Jul 1, 2017
@Throne3d Throne3d deleted the upgrade/migrate-to-irc-upd branch July 1, 2017 18:56
@ekmartin
Copy link
Member

ekmartin commented Jul 1, 2017

I've added you as an owner of the npm package - wanna try publishing a release for this, #256, #257 and the Doppins dependency upgrades? The process is basically:

  • Add a CHANGELOG.md entry for the changes.
  • Run either npm version minor or npm version patch, depending on if you think the emoji changes should be considered a new feature or not.
  • Push it to master.
  • Run npm publish.

@Throne3d
Copy link
Collaborator Author

Throne3d commented Jul 1, 2017

Sure! I'll get to doing that.

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.

Messages to IRC are split by character, not byte
3 participants