versions.properties

# Pinned component releases, maintained by .github/workflows/release.yml.
#
# Each component has a `.asset.pattern` beside its `.asset`: the pattern is
# what CI expands (@VERSION@ -> the new version) to work out what the next
# release's asset will be called. Helios' names carry no version, so its
# patterns are literals. @VERSION@ rather than ${VERSION} because Ant expands
# ${...} when it loads this file.
#
# To bump by hand: run `python3 -m tools.ci bump` to rewrite this file and the
# matching resource names in src/my/stepss/platform/Toolchain.java together.
# Editing only this file leaves Toolchain.java naming the old asset, which
# `ant jar` catches via PayloadManifestCheck.
ramses.version=3.82
ramses.repo=SPS-L/stepss-ramses
ramses.tag=v3.82
ramses.windows.asset=ramses-windows-x86_64-v3.82.zip
ramses.windows.asset.pattern=ramses-windows-x86_64-v@VERSION@.zip
ramses.windows.sha256=5079c021419eefe7492b339c28fb337923e131c370a0df80230a496dd927bfa9
ramses.linux.asset=ramses-linux-x86_64-v3.82.tar.gz
ramses.linux.asset.pattern=ramses-linux-x86_64-v@VERSION@.tar.gz
ramses.linux.sha256=1c08721e81f580481039fa7ca2e114292b5e2d83747afae63b854de2d77c73e4
ramses.macos.asset=ramses-macos-arm64-v3.82.tar.gz
ramses.macos.asset.pattern=ramses-macos-arm64-v@VERSION@.tar.gz
ramses.macos.sha256=b1a484405830741538457cf8345810408b88f28664e761536f010a731fa24ad6

helios.version=1.5.0
helios.repo=SPS-L/stepss-helios
helios.tag=v1.5.0
helios.windows.asset=stepss-helios-windows-x64.zip
helios.windows.asset.pattern=stepss-helios-windows-x64.zip
helios.windows.sha256=611fbb042301259411d27bea06c417c76758248b59fbb691d2bfeaf1383e95aa
helios.linux.asset=stepss-helios-linux-x86_64.tar.gz
helios.linux.asset.pattern=stepss-helios-linux-x86_64.tar.gz
helios.linux.sha256=0b02cd8f8f856a80bdae6467ab07ad10f8fb3e640abd209e8b371eb776a5acd5
helios.macos.asset=stepss-helios-macos-arm64.tar.gz
helios.macos.asset.pattern=stepss-helios-macos-arm64.tar.gz
helios.macos.sha256=903c0c08e995e3a785b8d9be57c9d695f84b9b88fc7fa12b1adb72e6d041095e

dyngraph.version=1.4.0
dyngraph.repo=SPS-L/stepss-dyngraph
dyngraph.tag=v1.4.0
dyngraph.windows.asset=dyngraph-windows-x86_64-v1.4.0.zip
dyngraph.windows.asset.pattern=dyngraph-windows-x86_64-v@VERSION@.zip
dyngraph.windows.sha256=cfb8912f6ef867d69e028968c86e4305d4d6db50703654e6e9d322bea069f817
dyngraph.linux.asset=dyngraph-linux-x86_64-v1.4.0.tar.gz
dyngraph.linux.asset.pattern=dyngraph-linux-x86_64-v@VERSION@.tar.gz
dyngraph.linux.sha256=442a38d525a776d3bfebe58ba2f350388e0b82ee0bf376f08c38ec0114d00df5
dyngraph.macos.asset=dyngraph-macos-arm64-v1.4.0.tar.gz
dyngraph.macos.asset.pattern=dyngraph-macos-arm64-v@VERSION@.tar.gz
dyngraph.macos.sha256=606261be53c87dd89d0240f3c5878503035f5415da235915d8498f598bdc2e3c
# All three dyngraph builds now come from the release. The Windows one is
# console (BUILDINFO: interface console), like Linux and macOS, so it replaces
# the committed Intel dialog build and every platform runs the same program in
# a terminal. The dialog observable picker existed only in that Intel build and
# is gone with it.

codegen.version=5.4
codegen.repo=SPS-L/stepss-codegen
codegen.tag=v5.4
codegen.windows.asset=codegen-windows-x86_64-v5.4.zip
codegen.windows.asset.pattern=codegen-windows-x86_64-v@VERSION@.zip
codegen.windows.sha256=7d5719bc69386cc0a0c868175b2e9ef35f65bbee1733c54a4f32ef2331e6e7dc
codegen.linux.asset=codegen-linux-x86_64-v5.4.tar.gz
codegen.linux.asset.pattern=codegen-linux-x86_64-v@VERSION@.tar.gz
codegen.linux.sha256=fc8cdb73adca5dfad5059c7f8e83efe8f84300193d0600432e73ea8167d00abd
codegen.macos.asset=codegen-macos-arm64-v5.4.tar.gz
codegen.macos.asset.pattern=codegen-macos-arm64-v@VERSION@.tar.gz
codegen.macos.sha256=17c62b2ab598ae9731db24428b9495bdf40e56937fe27d7baa34be545f319148

# stepss-uramses is the one PUBLIC component, so this payload is fetched over
# plain HTTPS with no gh and no STEPSS_TOKEN. GitHub's auto-generated source
# archives are not guaranteed byte-stable - a compression change on their side
# in early 2023 altered checksums for already-published tags - so the pin below
# is the SHA-256 of a content manifest over the files we retain, not of the
# downloaded container. Re-compression is invisible to it; a changed byte in
# any retained file is not.
uramses.version=3.82
uramses.repo=SPS-L/stepss-uramses
uramses.tag=v3.82
uramses.source.url=https://github.com/SPS-L/stepss-uramses/archive/refs/tags/v3.82.zip
uramses.source.url.pattern=https://github.com/SPS-L/stepss-uramses/archive/refs/tags/v@VERSION@.zip
uramses.manifest.sha256=c47275ff4991de3d1c6a42c1fb5cd6733f2c3589d7386faa51f2bce9ce2a5b21

# The bundled example test systems, offered by File > Open Examples.
#
# Pinned exactly like uramses above and for the same reasons: these are public
# repositories, so the source archive is fetched over plain HTTPS with no gh
# and no STEPSS_TOKEN, and the digest is over a CONTENT MANIFEST rather than
# over the downloaded archive, because GitHub's generated source archives are
# not guaranteed byte-stable.
#
# Two ways they differ from every other pin here, both deliberate:
#
#   * The packed payload name carries NO version (payload/example-<id>.zip), so
#     there is no second file naming it and nothing for Toolchain.java to keep
#     in step. An example bump touches this file and nothing else. That is safe
#     because ToolExtractor folds the application version into its staleness
#     stamp, which is what already makes the helios assets work.
#
#   * A new example release does NOT cut a STEPSS release. tools/ci reports
#     these as `refreshed` rather than `changed`, and release.yml's `proceed`
#     counts only `changed`, so an example rides along with the next real
#     release instead of triggering one. "An example repository got a typo fix
#     in its README" is not a reason to publish a new STEPSS.
#
# What goes IN each payload is not here: src/my/stepss/examples/examples.properties
# names the files, and ExamplesPack fails the build if a pinned release stops
# carrying one of them.

kundur.version=1.4.0
kundur.repo=SPS-L/stepss-Kundur-Two-Area-System
kundur.tag=v1.4.0
kundur.source.url=https://github.com/SPS-L/stepss-Kundur-Two-Area-System/archive/refs/tags/v1.4.0.zip
kundur.source.url.pattern=https://github.com/SPS-L/stepss-Kundur-Two-Area-System/archive/refs/tags/v@VERSION@.zip
kundur.manifest.sha256=912cd4eeb1ec79631b7c3feed079acaacf1e4418c9268a9a65ded82a1e8ecf81

nordic.version=1.3.0
nordic.repo=SPS-L/stepss-IEEE-Nordic-Test-system
nordic.tag=v1.3.0
nordic.source.url=https://github.com/SPS-L/stepss-IEEE-Nordic-Test-system/archive/refs/tags/v1.3.0.zip
nordic.source.url.pattern=https://github.com/SPS-L/stepss-IEEE-Nordic-Test-system/archive/refs/tags/v@VERSION@.zip
nordic.manifest.sha256=0c68523256eb2801d858420b8fec3598d39b7e78319f665e3f41256cdfa73ce3

five-bus.version=1.2.0
five-bus.repo=SPS-L/stepss-5-bus-test-system
five-bus.tag=v1.2.0
five-bus.source.url=https://github.com/SPS-L/stepss-5-bus-test-system/archive/refs/tags/v1.2.0.zip
five-bus.source.url.pattern=https://github.com/SPS-L/stepss-5-bus-test-system/archive/refs/tags/v@VERSION@.zip
five-bus.manifest.sha256=ee3a735ccec36bad68d05952381d0fd3aa29626d6345b7cb51dcf4a7c1e2ce00

six-bus.version=1.1.0
six-bus.repo=SPS-L/stepss-6-bus-MG
six-bus.tag=v1.1.0
six-bus.source.url=https://github.com/SPS-L/stepss-6-bus-MG/archive/refs/tags/v1.1.0.zip
six-bus.source.url.pattern=https://github.com/SPS-L/stepss-6-bus-MG/archive/refs/tags/v@VERSION@.zip
six-bus.manifest.sha256=972b421983be648952f63c59bed6cc091c84e9933e839729bf8f9553f6ea24bc