Skip to content

Conversation

@twerthi
Copy link
Contributor

@twerthi twerthi commented Dec 8, 2025


Background

The grate project changed the assets for the self-contained versions of the executable. Version 1.6.1 was the last version the old method was used, the code has been updated to take this into consideration so if the user specifies 1.6.1 or lower, it will use the old method for backwards compatibility when choosing to dynamically download the executable.

Results

The template will function correctly when choosing the dynamic download option for the latest versions and remain backwards compatible with 1.6.1

Before

The template was failing when choosing the dynamic download option.

After

Code now executes correctly for new versions as well as 1.6.1 and below.

Pre-requisites

  • Id should be a GUID that is not 00000000-0000-0000-0000-000000000000
    • NOTE If you are modifying an existing step template, please make sure that you do not modify the Id property (updating the Id will break the Library sync functionality in Octopus).
  • Version should be incremented, otherwise the integration with Octopus won't update the step template correctly
  • Parameter names should not start with $
  • Step template parameter names (the ones declared in the JSON, not the script body) should be prefixed with a namespace so that they are less likely to clash with other user-defined variables in Octopus (see this issue). For example, use an abbreviated name of the step template or the category of the step template).
  • LastModifiedBy field must be present, and (optionally) updated with the correct author
  • The best practices documented here have been applied
  • If a new Category has been created:
    • An image with the name {categoryname}.png must be present under the step-templates/logos folder
    • The switch in the humanize function in gulpfile.babel.js must have a case statement corresponding to it

Fixes an issue I discovered.

@github-actions
Copy link

github-actions bot commented Dec 8, 2025

Start Hyponome locally

docker pull ghcr.io/hnrkndrssn/hyponome:main
docker run --rm -p 8000:8080 -it ghcr.io/hnrkndrssn/hyponome:main

Review in Hyponome

Copy link
Contributor

@hnrkndrssn hnrkndrssn left a comment

Choose a reason for hiding this comment

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

there's, what looks like, a debug message on line 255, should this be included?

Copy link
Contributor

@hnrkndrssn hnrkndrssn left a comment

Choose a reason for hiding this comment

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

I'll mark this as approved and leave it up to you if you want the log message in there or not.

@twerthi twerthi merged commit aa86f4e into master Dec 9, 2025
2 checks passed
@twerthi twerthi deleted the update-grate branch December 9, 2025 15:53
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