-
Notifications
You must be signed in to change notification settings - Fork 70
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
Possible to get a release of v4.2.0? I need AngularJS 1.6+ compatibility. #103
Comments
Sure, I can publish a new version.
There are some commits on master after the v4.2.0 tag, can you see
whether you want them too? I could release v4.2.1 with those changes and
publish it.
|
Wow, thanks for the quick response, Joe! |
I tried publishing the new version today, but npm said:
Looks like an npm user called antony is the maintainer of the package: (By any chance might that be you, @antony?) |
@sbleon what should we do about updating this in NPM for you? Do you want to reach out the package maintainer since they haven't responded here? |
Thanks for the reminder, Joe. It looks like @antony is the right person. I'll see if I can reach him via other channels. It looks like it might be a couple of weeks but I'll let you know what happens. If we can get publishing rights for the package, are you interested in being a maintainer in npm? If so, what's your npm username? |
Heya. On holiday at the moment so didn't spot this. I've not used angular in a few years since switching to Svelte, so I'm happy to add some maintainers to the project. I will do so once I'm back from holiday if there are any volunteers? :) |
Antony, that would be great! Please add me as a maintainer when you get a
chance. I'm on npm with this same username: sbleon.
…On Sun, Jan 19, 2020 at 12:46 AM Antony Jones ***@***.***> wrote:
Heya. On holiday at the moment so didn't spot this. I've not used angular
in a few years since switching to Svelte, so I'm happy to add some
maintainers to the project.
I will do so once I'm back from holiday if there are any volunteers? :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#103?email_source=notifications&email_token=AABQQN3CAIM6LEGU2RAPBNTQ6PSK5A5CNFSM4J6CMS52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJKJUDA#issuecomment-575969804>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQQN2IXQ5BURAMAUMYBALQ6PSK5ANCNFSM4J6CMS5Q>
.
|
@sbleon done! |
Thanks, Antony! I was able to release 4.2.0.
…On Fri, Jan 24, 2020 at 8:35 AM Antony Jones ***@***.***> wrote:
@sbleon <https://github.com/sbleon> done!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#103?email_source=notifications&email_token=AABQQN2TXVXJTAGDNF7DXLTQ7LVARA5CNFSM4J6CMS52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ2ZPNI#issuecomment-578131893>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQQN2AW2WVHPNRZ5DG4J3Q7LVARANCNFSM4J6CMS5Q>
.
|
I'm currently using v4.2.0 via a Github URL in my package.json, because v4.2.0 is not yet on NPM. I'd love to avoid having to pull this package from Github. Any chance of getting a newer release?
The text was updated successfully, but these errors were encountered: