gcalcli
gcalcli copied to clipboard
insanum
Release v4.4.0
Process bug for preparing 4.4.0 release.
Mostly just here to serve as a comment thread for discussing the release...
I've finished all the tasks I'd planned for the 4.4 release except for any straightforward auth improvements (and getting more PRs merged). @mdengler could you look through my 2 PRs I sent you #694 and #700?
Then @insanum @jcrowgey we'll need permission to push an update to PyPI. Is it doable to grant me access to that?
And then my focus for remaining changes will be revisiting auth, #692. I'll be digging in to investigate how it's currently set up and possible directions, but I could use more eyes on that discussion.
I've now landed all the changes I was hoping to get into a 4.4 release!
Just figuring out publishing logistics now...
@jcrowgey can you grant me access to push gcalcli to testpypi and pypi? Looks like you and @tresni are the only ones with access. Some details at https://pypi.org/help/#project-name.
I'm certainly not opposed to doing so! It may take a minute to dig up my own credentials, tho.
On August 27, 2024 1:28:32 PM PDT, David Barnett @.***> wrote:
@jcrowgey can you grant me access to push gcalcli to testpypi and pypi? Looks like you and @tresni are the only ones with access. Some details at https://pypi.org/help/#project-name.
-- Reply to this email directly or view it on GitHub: https://github.com/insanum/gcalcli/issues/706#issuecomment-2313451832 You are receiving this because you were mentioned.
Message ID: @.***>
It took me a minute, but I was able to recovery my pypi account. What is your pypi identity?
On Tue, Aug 27, 2024 at 01:28:32PM -0700, David Barnett wrote:
@jcrowgey can you grant me access to push gcalcli to testpypi and pypi? Looks like you and @tresni are the only ones with access. Some details at https://pypi.org/help/#project-name.
-- Reply to this email directly or view it on GitHub: https://github.com/insanum/gcalcli/issues/706#issuecomment-2313451832 You are receiving this because you were mentioned.
Message ID: @.***>
It's https://pypi.org/user/dbarnett/ + https://test.pypi.org/user/mu_mind/. Thanks!
Release is live on PyPI! https://pypi.org/project/gcalcli/4.4.0/
Now to get to work on the real fun in the next milestone, 4.5: https://github.com/insanum/gcalcli/milestone/10
Hi @dbarnett, I have not been able to look at this until now. Two things of note that I added earlier are:
- new
agendaupdatesubcommand (#550/#557/#577): this allows bulk changes with a whole TSV full of events to be updated - As part of this,
agendaupdate --tsvnow has a header row (97e21b17d8e2e9bc682eccd9cdba9ce6cbc0161a). This enables easier editing withagendaupdatewhich requires it. But it's also a breaking change for anything that expected to use the TSV output without a header row. I intended that the next version might be a major release because of this but of course have not been able to keep up.
I have some scripts I could post somewhere to demonstrate how to use these, but they were designed entirely for my own use and do not meet the usual standard for gcalcli code (that is not sarcasm—despite frequent complaints in the issue tracker, I use gcalcli daily, and it works quite well for me), so probably don't belong in the main repo.
Also, please accept my personal thanks for taking on the leadership of this project. Very much appreciated.
Couldn't agree more. Much appreciation. David, you've been a machine! :-)
On Mon, Sep 16, 2024 at 11:37 AM Michael Hoffman @.***> wrote:
Also, please accept my personal thanks for taking on the leadership of this project. Very much appreciated.
— Reply to this email directly, view it on GitHub https://github.com/insanum/gcalcli/issues/706#issuecomment-2353642410, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD55I5IP7VOWNSMWTZZ7R3ZW4QOFAVCNFSM6AAAAABNCBYIF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJTGY2DENBRGA . You are receiving this because you were mentioned.Message ID: @.***>
Aww, thank you! It's been really cool being able to jump into the gcalcli project you've built and revitalize things. :heart:
@michaelmhoffman happy to help get your agendaupdate changes moving again. I'm still trying to get my head around the changes there and current status. Shall I follow up on #550 with general questions/clarifications, or is there a different place to discuss that'd work better?
I am much more responsive over email. My GitHub notifications are overwhelming, frankly.