Skip to content

Update pyrevit-hosts.json - 2023.1.9#3180

Merged
jmcouffin merged 1 commit intopyrevitlabs:developfrom
924312:patch-4
Mar 24, 2026
Merged

Update pyrevit-hosts.json - 2023.1.9#3180
jmcouffin merged 1 commit intopyrevitlabs:developfrom
924312:patch-4

Conversation

@924312
Copy link
Copy Markdown
Contributor

@924312 924312 commented Mar 17, 2026

Add 2023.1.9

Copy link
Copy Markdown
Contributor

@devloai devloai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary:

  • Adds a new Revit 2023.1.9 host entry to bin/pyrevit-hosts.json
  • Build: 20260220_1515, Version: 23.1.90.15
  • Release date: February 2026
  • All field values verified against official Autodesk release notes

Review Summary:

The version number, build identifier, and source/notes URLs for Revit 2023.1.9 are all correct and match Autodesk's official release documentation. However, the entry was inserted in the wrong position in the file. pyrevit-hosts.json enforces chronological ordering by build date, and this entry's build date (20260220_1515, Feb 2026) makes it the most recent entry in the file — it should be appended at the end of the array, not placed mid-file between the 2023.x and 2024.x series.

Follow-up suggestions:

  • @devloai fix the identified chronological ordering issue by moving the 2023.1.9 entry to the end of the JSON array

@924312
Copy link
Copy Markdown
Contributor Author

924312 commented Mar 17, 2026

I mean I guess you could interpret it as Chronological ordering by build date enforced
It does not explicitly say that though

!!! note Build numbers are released by Autodesk with each update. Add new entries as updates are released.

It doesn't look like any other parts of this file are sorted by build date, and it's my personal opinion that that would be a stupid way to sort it anyway

@jmcouffin
Copy link
Copy Markdown
Contributor

that would be a stupid way

Agreed
Revit year/build-date is more sensible.

@jmcouffin jmcouffin merged commit f128b3f into pyrevitlabs:develop Mar 24, 2026
@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26083+2045-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26083+2048-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26083+2106-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26083+2130-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26086+2004-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26088+1318-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26089+1231-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+0549-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+1533-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+1536-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+1540-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+1540-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New work-in-progress (wip) builds are available for 6.1.0.26090+1556-wip

@github-actions
Copy link
Copy Markdown
Contributor

📦 New public release are available for 6.2.0.26090+1754

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.

2 participants