Skip to content

Conversation

IanButterworth
Copy link
Member

Tried a resolve but it needed to change deps.

(documenter) pkg> resolve
     Project No packages added to or removed from `~/Documents/GitHub/julia/deps/jlutilities/documenter/Project.toml`
    Updating `~/Documents/GitHub/julia/deps/jlutilities/documenter/Manifest.toml`
  [3161d3a3] - Zstd_jll v1.5.7+1
  [f43a241f] ↓ Downloads v1.7.0 ⇒ v1.6.0
  [44cfe95a] ↓ Pkg v1.13.0 ⇒ v1.12.0
  [e66e0078] - CompilerSupportLibraries_jll v1.3.0+1
  [deac9b47] ↓ LibCURL_jll v8.16.0+0 ⇒ v8.11.1+1
  [e37daf67] ↓ LibGit2_jll v1.9.1+0 ⇒ v1.9.0+0
  [14a3606d] ↓ MozillaCACerts_jll v2025.9.9 ⇒ v2025.5.20
  [458c3c95] ↓ OpenSSL_jll v3.5.4+0 ⇒ v3.5.1+0
  [efcefdf7] ↓ PCRE2_jll v10.46.0+0 ⇒ v10.44.0+1
  [8e850ede] ↓ nghttp2_jll v1.67.1+0 ⇒ v1.64.0+1
  [3f19e933] ↓ p7zip_jll v17.6.0+0 ⇒ v17.5.0+2

I'm not sure why stdlibs are being precompiled during docs build, given it uses 1 i.e. 1.12

https://buildkite.com/julialang/julia-master/builds/51254#0199cd68-2600-4a7f-957b-c665df1a3bce/1043-1045

@giordano
Copy link
Member

I thought you said we can simply delete the manifests: #56976 (comment)

@IanButterworth
Copy link
Member Author

This is the docs manifest. Previously people have wanted to lock the docs versions (I'd be open to deleting it)

@DilumAluthge
Copy link
Member

DilumAluthge commented Oct 10, 2025

I think we should keep the manifest for docs for now, but perhaps in the future we could:

  1. Version these manifests. EDIT: I don't believe that to be necessary.
  2. Fix julia-Buildkite to install specific Julia versions, instead of installing '1', which will cause things to suddenly break when new Julia versions are installed.

I'm going to try work on number 2 soon.

@DilumAluthge DilumAluthge self-assigned this Oct 10, 2025
@DilumAluthge
Copy link
Member

Let me first get a PR into julia-buildkite - I'll mark this as draft.

@DilumAluthge DilumAluthge marked this pull request as draft October 10, 2025 13:44
@DilumAluthge
Copy link
Member

I might be misunderstanding, but: shouldn't this target the release-12 branch? And then master will use 1.13?

@DilumAluthge
Copy link
Member

Looking into this, I don't think this is correct. The docs manifest that is checked in to Git should match the Julia version on that Git commit. So, currently on master the Julia version is 1.13-DEV, and thus the docs manifest should also be 1.13-DEV.

When I look at master (https://buildkite.com/julialang/julia-master/builds?branch=master), it looks like all the docs CI jobs are green - they were fixed when https://github.com/JuliaCI/sandbox-buildkite-plugin/releases/tag/v2.2 was tagged.

@IanButterworth IanButterworth deleted the ib/docs_manifest branch October 11, 2025 21:25
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

Successfully merging this pull request may close these issues.

3 participants