starred/ArchiveBox

Fork 0

mirror of https://github.com/ArchiveBox/ArchiveBox.git synced 2026-04-25 17:16:00 +03:00

[GH-ISSUE #1132] Request to bump PyPi version from v0.6.2 to latest changes from v0.6.3/dev #711

New issue

Closed

opened 2026-03-01 14:45:43 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 14:45:43 +03:00

Owner

Originally created by @turian on GitHub (Apr 2, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1132

Given recent update and merges, could you push a new pypi version?
Even if it's marked as beta, it would be useful to collect feedback

Originally created by @turian on GitHub (Apr 2, 2023). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1132 Given recent update and merges, could you push a new pypi version? Even if it's marked as beta, it would be useful to collect feedback

kerem

2026-03-01 14:45:43 +03:00

closed this issue
added the
expected: next release

status: wip
labels

kerem commented

2026-03-01 14:45:44 +03:00

Author

Owner

@pirate commented on GitHub (Jun 13, 2023):

Closing this for now as I'm doing a github issue cleanup pass, trust that I'm well aware of the pressure to roll a new PyPI release 💜

The main blocker for pypi is the difficult django version upgrade here: https://github.com/ArchiveBox/ArchiveBox/issues/988 (which may take months still)

Subscribe to that issue for more granular updates for now

I am working through a backlog of issues that need to be fixed before I am ready to roll the next "stable" release. I understand this is annoying for users accustomed to the much more rapid monthly release cycle of other homelab apps like Plex, Nextcloud, etc. (as I would be too!).

Because there are a bunch of slow-moving orgs that depend on the bare-metal (pypi/brew/pkg) ArchiveBox releases being non-breaking, I would rather direct users expecting faster bugfixes to the Docker archivebox/archivebox:dev image (until I am ready to roll a new stable release). The bare-metal users are able to upgrade the core & their extractor dependencies independently, and the Docker users are able to use :dev which bundles the most recent dependencies, so most users have a reasonably accessible solution to running up-to-date ArchiveBox if they need it urgently.

I'm still just a solo dev on this project, my time budget for ArchiveBox has been 1~2 days a month for the last 1.5yr, limiting me to mostly answering support requests, improving docs, reviewing PRs, and pushing security fixes. The most recent release delay is partly a function of me accepting too many feature requests (increasing the surface area that I have to bugfix), and partly a function of ArchiveBox's core design philosophy which depends on a lot of external extractor tools that change often.

I have started to devote more dedicated energy to ArchiveBox in the last month again, but it will take me some time to ramp up and work through the backlog and prepare a new stable Docker release.

In the meantime please check out the most recently updated Github Issues / Discussions, and @ArchiveBoxApp Twitter for updates.

@pirate commented on GitHub (Jun 13, 2023): Closing this for now as I'm doing a github issue cleanup pass, trust that I'm well aware of the pressure to roll a new PyPI release 💜 The main blocker for pypi is the difficult django version upgrade here: https://github.com/ArchiveBox/ArchiveBox/issues/988 (which may take months still) Subscribe to that issue for more granular updates for now --- I am working through a backlog of issues that need to be fixed before I am ready to roll the next "stable" release. I understand this is annoying for users accustomed to the much more rapid monthly release cycle of other homelab apps like Plex, Nextcloud, etc. (as I would be too!). Because there are a bunch of slow-moving orgs that depend on the bare-metal (pypi/brew/pkg) ArchiveBox releases being non-breaking, I would rather direct users expecting faster bugfixes to the Docker `archivebox/archivebox:dev` image (until I am ready to roll a new stable release). The bare-metal users are able to upgrade the [core](https://github.com/ArchiveBox/ArchiveBox#install-and-run-a-specific-github-branch) & their extractor dependencies independently, and the Docker users are able to use `:dev` which bundles the most recent dependencies, so most users have a reasonably accessible solution to running up-to-date ArchiveBox if they need it urgently. I'm still just a solo dev on this project, my time budget for ArchiveBox has been 1~2 days a month for the last 1.5yr, limiting me to mostly answering support requests, improving docs, reviewing PRs, and pushing security fixes. The most recent release delay is partly a function of me accepting too many feature requests (increasing the surface area that I have to bugfix), and partly a function of ArchiveBox's core design philosophy which depends on a lot of external extractor tools that change often. I have started to devote more dedicated energy to ArchiveBox in the last month again, but it will take me some time to ramp up and work through the backlog and prepare a new stable Docker release. In the meantime please check out the [most recently updated Github Issues](https://github.com/ArchiveBox/ArchiveBox/issues?q=is%3Aopen+is%3Aissue) / [Discussions](https://github.com/ArchiveBox/ArchiveBox/discussions), and [@ArchiveBoxApp Twitter](https://twitter.com/ArchiveBoxApp) for updates.

kerem referenced this issue

2026-03-01 17:55:19 +03:00

[GH-ISSUE #711] Bug: 500 error after upgrade #1955

kerem referenced this issue

2026-03-14 23:03:47 +03:00

[GH-ISSUE #711] Bug: 500 error after upgrade #3465

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ArchiveBox#711

No description provided.

Rows
Columns