Re: [ANN] Important upcoming changes to Clojars

2021-04-18 Thread Toby Crawley
These changes have now been completed - you will need to use a verified group when deploying a *new* project to Clojars. These changes will only impact folks deploying to Clojars; consumption of artifacts from Clojars is unchanged. A summary of the current state: - *existing* projects can

Re: [ANN] Important upcoming changes to Clojars

2021-03-26 Thread Toby Crawley
A followup on: On Monday, March 1, 2021 at 8:47:05 AM UTC-5 Toby Crawley wrote: > # Dropping support for old Java versions > > The repository itself is hosted behind a Fastly CDN, and Fastly is forcing > all accounts to switch to SNI[1] for TLS connections. Clojars will be > migrated on or

Re: [ANN] Important upcoming changes to Clojars

2021-03-01 Thread Toby Crawley
On Mon, Mar 1, 2021, at 11:08, James Reeves wrote: > Have you considered automatically validating domain name ownership by > supplying a challenge token and then looking for it at a well-known location > on the domain? That's a good suggestion - I have considered that as a verification option.

Re: [ANN] Important upcoming changes to Clojars

2021-03-01 Thread James Reeves
This is an interesting change, and essentially enforces a de-facto package naming scheme for Clojure. I don't see this as a bad thing, though. Have you considered automatically validating domain name ownership by supplying a challenge token and then looking for it at a well-known location on

[ANN] Important upcoming changes to Clojars

2021-03-01 Thread Toby Crawley
Howdy folks! We have two separate changes coming for the Clojars system that you need to be aware of. First, the tl;dr: - After 2021-04-15, versions of Java older than 7u25 will no longer be able to access the Clojars repository - After 2021-04-18, a Clojars group name must have verified

Re: Upcoming changes to Clojars

2020-01-04 Thread Toby Crawley
We haven't gotten any objections to these changes to Clojars, so have implemented them. The changes are: - rsyncing of the Clojars repo is now disabled (see https://github.com/clojars/clojars-web/issues/735) - GET or HEAD requests to the on-disk repo will now redirect to the CDN-fronted repo (see

Re: Upcoming changes to Clojars

2019-12-23 Thread Toby Crawley
Thanks for asking Sean. The upload URL and process will *not* be changing. This change should have no impact for 99% of Clojars users. - Toby On Mon, Dec 23, 2019 at 4:43 PM Sean Corfield wrote: > > Will the upload URL or process be changing? > > On Mon, Dec 23, 2019 at 9:51 AM Toby Crawley

Re: Upcoming changes to Clojars

2019-12-23 Thread Sean Corfield
Will the upload URL or process be changing? On Mon, Dec 23, 2019 at 9:51 AM Toby Crawley wrote: > Howdy folks! We're in the process of making some changes to the > Clojars infrastructure to make it more robust, reliable, and easier to > maintain. One of those changes will be to provide a single

Upcoming changes to Clojars

2019-12-23 Thread Toby Crawley
Howdy folks! We're in the process of making some changes to the Clojars infrastructure to make it more robust, reliable, and easier to maintain. One of those changes will be to provide a single canonical repository instead of serving artifacts from two locations. ## A Tale of Two Repositories