Skip to content
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

New release soon? #377

Closed
randycoulman opened this issue Sep 13, 2018 · 5 comments
Closed

New release soon? #377

randycoulman opened this issue Sep 13, 2018 · 5 comments

Comments

@randycoulman
Copy link

I've experienced the problem described in #368 and #276. It appears to be fixed by #356 which has been merged but not released. I checked out a local copy of master to verify, and it certainly fixes the problem for me.

Would it be possible to get a new release of this extension that includes this fix?

Is there anything I can do to help make that happen?

Thanks!

@connectdotz
Copy link
Collaborator

there are a couple of minor changes since 2.9.0, I think we can certainly cut a 2.9.1, @orta what do you think?

@orta
Copy link
Member

orta commented Sep 16, 2018

Yep - makes sense shipped!

@orta orta closed this as completed Sep 16, 2018
@randycoulman
Copy link
Author

@orta Thanks! I'm not seeing it in the marketplace yet, though. Is there usually some kind of delay before that happens?

@smrpr
Copy link

smrpr commented Sep 26, 2018

I can't see it either. cc @orta

@orta
Copy link
Member

orta commented Sep 26, 2018

Alright.- yeah, looks like my vscode push access token hit it's annual expiration - just shipped it, thanks for the reminders

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

No branches or pull requests

4 participants