When will the fix for django 3.2 be released? about django-revproxy

[andruten]

@brianmay Could you please publish a new release? :) Thanks!

[andruten]

Finally, version 0.11.0 has been released 🥲

I'm closing this.

[andruten]

I think a new release could be released as some tasks from #129 have been resolved.

[brianmay]

Unfortunately I have no time to even look at this package. Is the CHANGELOG.rst up to date for the next release? If not it would help if somebody provided a PR to update this.

[andruten]

Done! #162

[brianmay]

My 1st attempt to release failed. https://github.com/jazzband/django-revproxy/actions/runs/4267415470/jobs/7428996053

Probably something trivial wrong, no idea what.

[andruten]

Thank you! I'm looking into this...

[brianmay]

Looks like not set to me. Similar if I click variables.

[andruten]

Ok, thank you! Who could add that secrets? 🤔

I've joined the Jazzband organization and I've assigned to myself as a team member.

I think I can publish releases and manage issues now but my PRs still need at least one approval.

[brianmay]

Lets see then if you can publish this release :-)

[andruten]

Yes! :D I've merged it and I've created a new release... Hope it works...

[andruten]

Not yet as 0.11.0 is not available in PyPi. There is an issue in the jazzband/help repository.

[brianmay]

No, that is not a work around we can implement. It is just asking the user to download djang-revproxy from github instead of PyPi.

[acangiani]

Ok, sorry for creating noise, very much appreciate it.

[brianmay]

I think we need to fix the items in #129 first. At least as many as possible.

Unfortunately, I simply do not have time to look at this.

[smit-mehta25]

@seocam @brianmay Any updates on this one?

[JeroenJADS]

This has been fixed in #148!

[chiatt]

Hi @JeroenJADS, this fix works great, but to @my-umd's question, it's not yet released on PyPi. This is a problem because the latest django-revproxy (with the fix) can't be used as a dependency in a requirements.txt file for a project published on PyPi. Locally the github url to the master branch can be used, but PyPi will reject that for security reasons.

[matjazsu]

Hi @JeroenJADS,

Hi @JeroenJADS, this fix works great, but to @my-umd's question, it's not yet released on PyPi. This is a problem because the latest django-revproxy (with the fix) can't be used as a dependency in a requirements.txt file for a project published on PyPi. Locally the github url to the master branch can be used, but PyPi will reject that for security reasons.

any news regarding ^^?

[medihack]

I can confirm that the current master branch works correctly with Django 4.1. So a new release would be nice.

[andruten]

Thank you for your time. I'll take a look. I think this is happening because of the version declared in the __init__.py file.

[andruten]

#163 may fix the issue :).

[andruten]

@brianmay 0.11.0 tag may be removed and recreated again using HEAD commit of master branch. Thanks in advance.

[andruten]

I see it is still giving 500 error during upload process... :(

[brianmay]

I did that, but it didn't work out. Oh, crap that was my fault. Somehow I thought my git repo was up-to-date when it wasn't which led to a sequence of errors on my end.

Yes, still not working. No idea why.

[andruten]

@brianmay Is the JAZZBAND_RELEASE_KEY secret filled?

[brianmay]

Not 100% sure, but it doesn't look like it to me.

[andruten]

Once secret it's set you can't see it anymore. You may see it blank but it can be there.

[andruten]

I'll remove 0.11.0 and 0.11.1 tags and I'll recreate again.

[brianmay]

Sounds good. Don't forget to update the CHANGELOG.rst and revproxy/__init__.py files also :-)

[andruten]

Oops! On it!

[andruten]

Done!

[brianmay]

Approved. I think you should be able to merge it. Once the CI is done.

[brianmay]

Doesn't look good :-(

[andruten]

It didn't 🥲. I think this is related to that secret.

[andruten]

I've published an issue in jazzband help repository. I'll let you know...!

[medihack]

Can this be closed?

[acangiani]

@andruten or @brianmay there is a comment on how to fix the release of 0.11.0 on the Jazzband issue, can you try it out?