From: Zhihang Wei <wzh@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] Isar 1.1
Date: Wed, 6 May 2026 17:00:33 +0200 [thread overview]
Message-ID: <20260506150033.3895606-1-wzh@ilbers.de> (raw)
---
ChangeLog | 4 ++++
RECIPE-API-CHANGELOG.md | 5 ++++-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index a264a0f7..63069c02 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
Release next
+Release v1.1
+
+ * Restore build artifacts naming and deploy path
+
Release v1.0
* Add Debian Trixie support to various machines
diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
index 659a03b0..2d210635 100644
--- a/RECIPE-API-CHANGELOG.md
+++ b/RECIPE-API-CHANGELOG.md
@@ -1059,7 +1059,7 @@ same TMPDIR in OpenEmbedded, conflicts may occur and are not handled by
OE. Artifacts with the same name overwrite each other, leading to
incorrect build results.
-Changes in next
+Changes in v1.1
---------------
### Revert "Change DEPLOY_DIR_IMAGE path and artifacts naming"
@@ -1067,3 +1067,6 @@ Changes in next
The DEPLOY_DIR_IMAGE path and artifacts naming changes introduced in
13cb77dd (included in Isar v1.0) have been reverted. Deployment paths
and artifact names are the same as pre-v1.0.
+
+Changes in next
+---------------
--
2.39.5
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260506150033.3895606-1-wzh%40ilbers.de.
next reply other threads:[~2026-05-06 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 15:00 Zhihang Wei [this message]
2026-05-06 15:05 ` Zhihang Wei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260506150033.3895606-1-wzh@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox