What is the timeline for a 0.9.3 release with: https://github.com/facebook/relay/commit/dcc97a431af719b71b62506ce8fe29b85158ef3e included?
@cancan101, I am planning on cutting a release this week. I'll update this issue if anything unexpected comes up that would delay it.
awesome, just noticed you published the latest version of relay, but babel-relay-plugin is still on 0.9.2
can release it as well or does it require more work?
NPM warning
npm ERR! peer invalid: [email protected], required by [email protected]
I think there is something fishy with NPM. I can't see it on the releases page, but I definitely ran npm publish. If I try to run it again, in fact, I get this:
npm ERR! "You cannot publish over the previously published version 0.9.3." : babel-relay-plugin
I might have to bump the version number and republish.
เฒ _เฒ
npm install babel-relay-plugin in an empty directory installs 0.9.3 for me and npm view babel-relay-plugin also shows 0.9.3 as the latest release. Looks like the npmjs website just has a caching issue?
Ok, I think I might have overreacted here because the listing on npmjs.com is busted. The package actually _is_ published. The reason you are seeing that message @nikgraf is because babel-relay-plugin is a peer-dependency. Under NPM 3, you have to supply it yourself.
/tmp$ mkdir demo 0.02s /tmp
/tmp$ cd demo 0.01s /tmp
. ..
demo$ npm init 0.01s /tmp/demo
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.
See `npm help json` for definitive documentation on these fields
and exactly what they do.
Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.
Press ^C at any time to quit.
name: (demo)
version: (1.0.0)
description:
entry point: (index.js)
test command:
git repository:
keywords:
author:
license: (ISC)
About to write to /private/tmp/demo/package.json:
{
"name": "demo",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC"
}
Is this ok? (yes)
demo$ npm install --save react-relay babel-relay-plugin react 3.63s /tmp/demo
[email protected] /private/tmp/demo
โโโฌ [email protected]
โ โโโฌ [email protected]
โ โโโ [email protected]
โโโฌ [email protected]
โ โโโฌ [email protected]
โ โ โโโ [email protected]
โ โ โโโ [email protected]
โ โ โโโฌ [email protected]
โ โ โ โโโฌ [email protected]
โ โ โ โ โโโฌ [email protected]
โ โ โ โ โ โโโ [email protected]
โ โ โ โ โโโ [email protected]
โ โ โ โโโ [email protected]
โ โ โโโฌ [email protected]
โ โ โ โโโ [email protected]
โ โ โโโ [email protected]
โ โโโฌ [email protected]
โ โ โโโ [email protected]
โ โโโ [email protected]
โโโฌ [email protected]
โโโฌ [email protected]
โ โโโ [email protected]
โ โโโ [email protected]
โโโ [email protected]
npm WARN [email protected] No description
npm WARN [email protected] No repository field.
demo$ cat package.json 5.82s /tmp/demo
{
"name": "demo",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"author": "",
"license": "ISC",
"dependencies": {
"babel-relay-plugin": "0.9.3",
"react": "15.3.1",
"react-relay": "0.9.3"
}
}
The fact that the listing on the webside has failed to update after over 12 hours is a separate issue that threw me off, and which I unfortunately don't think is likely to resolve itself until we publish a new version, but I don't think it is worth it.
Thanks for taking care of it!
Quite interesting. The website still shows me that 0.9.2 is the last uploaded version while npm view babel-relay-plugin versions shows the right results. Might be a caching issues โฆ
npm view babel-relay-plugin versions
[ '0.1.0',
'0.1.1',
'0.1.2',
'0.1.3',
'0.2.0',
'0.2.1',
'0.2.2',
'0.2.3',
'0.2.4',
'0.2.5',
'0.2.6',
'0.3.0',
'0.4.0',
'0.4.1',
'0.6.0',
'0.6.1',
'0.6.3',
'0.7.0-rc.2',
'0.7.0',
'0.7.1',
'0.7.2',
'0.7.3',
'0.8.0',
'0.8.1',
'0.9.0',
'0.9.1',
'0.9.2',
'0.9.3' ]

Most helpful comment
@cancan101, I am planning on cutting a release this week. I'll update this issue if anything unexpected comes up that would delay it.