Which version of nodeBB is running community.nodebb.org?

scottalanmiller

It says the version on the main landing page on the right hand side.

jarey

Probably something close to where the master branch is at.

It says the version on the main landing page on the right hand side.

Thanks, i saw the versión in the top right side of the page, but thought that maybe it is the last dev version, not necessary the las version running here.

Regards.

Schamper

@José-Ángel-Rey-Liñares said:

@scottalanmiller said:

It says the version on the main landing page on the right hand side.

Thanks, i saw the versión in the top right side of the page, but thought that maybe it is the last dev version, not necessary the las version running here.

Regards.

It says "latest version is x", so you'd expect that to be the actual last dev version, not the version running this forum.

jarey

@Schamper Got it. Thanks

Bobber

@Schamper Is there a good time to update 0.6.0 to 0.6.1 so plugins won't break?

Schamper

@Alex-Kuznetsof57 check if all the plugins you use are updated for 0.6.x compatibility.

Bobber

@Schamper Alright So checking first plugin and i don't see anything related to 0.6.x but rather just 0.6.0
that means i need to wait till developer updates info or it will work cause X mean all versions?

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

GitHub (github.com)

Aza Noriega

@Alex-Kuznetsof57 "compatibility": "^0.6.0" mean 0.6.0 and greater what mean the X in versions
Btw it looks like nodebb-plugin-amazons3 should works even on 0.7.0-dev

Bobber

@Mega Thanks buddy

codejet

@Bobber I've had only one plugin break I can see in upgrading from 0.6.0 -> 0.6.1 and that's the twitter embed plugin.

Don't ask me if it was working properly in 0.6.0 but I'm pretty sure it was. Surely it wouldn't be hard to fix this thing, being that the example plugin uses the same hook to embed a youtube video ? Didn't look hard

julian

If it was a patch upgrade (that is, only the right-hand-most digit changed: 0.6.0 -> 0.6.1), then you should be safe from broken plugins, as all changes are backwards compatible.

The real fun stuff happens when we go from 0.6.x to 0.7.x

Edit: I jest. 0.5.x to 0.6.x was harder than we expected, since we changed the static:app.init hook, which practically every plugin uses.

0.7.x has comparatively fewer breaking changes, but it is a long way out yet... :shipit: