abra app new <recipe> <version> always use env from main #862

Closed
opened 2026-06-09 11:11:59 +00:00 by moritz · 0 comments
Member

Bug in abra app new <recipe> <version>

Expected Behaviour

The recipe will be checked out to <version> and based on this version the .env will be generated

Current Behavior

abra app new always uses the newest .env of the main branch. This env can conflict the version that should be deployed and can have untested unreleased changes.

Possible Solution

This bug was introduced by this commit: https://git.coopcloud.tech/toolshed/abra/commit/dc4c6784cb#diff-94c1e19451212ceecf657163bdb4ddee2f17bb30
By removing Line 107 to 111:

		if !internal.Chaos && recipeVersion != "" {
				if _, err := recipe.EnsureVersion(recipeVersion); err != nil {
					log.Fatal(err)
				}
			}

Restoring these lines should solve the bug.

Bug in `abra app new <recipe> <version>` ## Expected Behaviour The recipe will be checked out to `<version>` and based on this version the .env will be generated ## Current Behavior `abra app new` always uses the newest .env of the main branch. This env can conflict the version that should be deployed and can have untested unreleased changes. ## Possible Solution This bug was introduced by this commit: https://git.coopcloud.tech/toolshed/abra/commit/dc4c6784cb#diff-94c1e19451212ceecf657163bdb4ddee2f17bb30 By removing Line 107 to 111: ``` if !internal.Chaos && recipeVersion != "" { if _, err := recipe.EnsureVersion(recipeVersion); err != nil { log.Fatal(err) } } ``` Restoring these lines should solve the bug.
moritz added the
bug
label 2026-06-09 11:11:59 +00:00
decentral1se added this to the Abra "next" project 2026-06-10 08:56:23 +00:00
decentral1se moved this to Done in Abra "next" on 2026-06-10 08:56:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#862
No description provided.