Re: [DISCUSS] gremlint 3.5.1 release candidate
Very cool! I gave it a quick test and it works! tor. 15. jul. 2021 kl. 16:45 skrev Stephen Mallette : > wow - first try: > > https://www.npmjs.com/package/gremlint > > > > > On Mon, Jul 12, 2021 at 2:28 PM Øyvind Sæbø wrote: > > > > > I don’t have a strong opinion on this, so if this is consistent with how > > it’s been done earlier it sounds good to me. Really excited to see we’re > > getting close to releasing Gremlint as a library:) > > > > Øyvind > > > > > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette : > > > > > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint > as > > a > > > library. To ensure that it's all rigged up properly to deploy to npm on > > > release day, i think it's worth trying to publish a release candidate > > with > > > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. > > > > > > I realize "-rc1" isn't exactly the way javascript numbers these sorts > of > > > things, but perhaps we should try to just stay consistent with what > we've > > > always done. My understanding is that the actual version number we use > > has > > > less to do with a "beta" or "alpha" version than the usage of the --tag > > > value as in: > > > > > > npm publish --tag beta > > > > > > Assuming there are no concerns I'll go ahead with this initial try for > > > 3.5.1-rc1 in the next day or so. Thanks! > > >
Re: [DISCUSS] gremlint 3.5.1 release candidate
wow - first try: https://www.npmjs.com/package/gremlint On Mon, Jul 12, 2021 at 2:28 PM Øyvind Sæbø wrote: > > I don’t have a strong opinion on this, so if this is consistent with how > it’s been done earlier it sounds good to me. Really excited to see we’re > getting close to releasing Gremlint as a library:) > > Øyvind > > > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette : > > > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint as > a > > library. To ensure that it's all rigged up properly to deploy to npm on > > release day, i think it's worth trying to publish a release candidate > with > > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. > > > > I realize "-rc1" isn't exactly the way javascript numbers these sorts of > > things, but perhaps we should try to just stay consistent with what we've > > always done. My understanding is that the actual version number we use > has > > less to do with a "beta" or "alpha" version than the usage of the --tag > > value as in: > > > > npm publish --tag beta > > > > Assuming there are no concerns I'll go ahead with this initial try for > > 3.5.1-rc1 in the next day or so. Thanks! >
Re: [DISCUSS] gremlint 3.5.1 release candidate
I don’t have a strong opinion on this, so if this is consistent with how it’s been done earlier it sounds good to me. Really excited to see we’re getting close to releasing Gremlint as a library:) Øyvind > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette : > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint as a > library. To ensure that it's all rigged up properly to deploy to npm on > release day, i think it's worth trying to publish a release candidate with > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. > > I realize "-rc1" isn't exactly the way javascript numbers these sorts of > things, but perhaps we should try to just stay consistent with what we've > always done. My understanding is that the actual version number we use has > less to do with a "beta" or "alpha" version than the usage of the --tag > value as in: > > npm publish --tag beta > > Assuming there are no concerns I'll go ahead with this initial try for > 3.5.1-rc1 in the next day or so. Thanks!
[DISCUSS] gremlint 3.5.1 release candidate
As we'd discussed elsewhere, 3.5.1 should be good to release gremlint as a library. To ensure that it's all rigged up properly to deploy to npm on release day, i think it's worth trying to publish a release candidate with a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. I realize "-rc1" isn't exactly the way javascript numbers these sorts of things, but perhaps we should try to just stay consistent with what we've always done. My understanding is that the actual version number we use has less to do with a "beta" or "alpha" version than the usage of the --tag value as in: npm publish --tag beta Assuming there are no concerns I'll go ahead with this initial try for 3.5.1-rc1 in the next day or so. Thanks!
