Compare commits

..
Author SHA1 Message Date
Jeremy Soller d103b64024 Update translations 2026-04-14 10:34:47 -06:00
Jeremy Soller 9af2199729 Update for 1.0.10 tags 2026-04-14 09:47:35 -06:00
Jeremy Soller 9e8ac99bcb Update for 1.0.9 tags 2026-04-07 14:34:23 -06:00
Jeremy Soller efe2c51b53 Prepare for next tag 2026-02-24 10:27:40 -07:00
Jeremy Soller 9b0e61c54b Prepare for next tag 2026-02-17 14:17:02 -07:00
Jeremy Soller f5fa41194e Update repos 2026-02-13 12:32:54 -07:00
Jeremy Soller f9abdc105d Add PR template 2026-02-13 12:21:16 -07:00
Jeremy Soller dee71b6f25 Update for 1.0.6 tag 2026-02-10 11:07:25 -07:00
Jeremy Soller d955da69d4 Prepare for 1.0.5 tag 2026-02-03 09:08:14 -07:00
Jeremy Soller 5dcb211692 Prepare for 1.0.4 tag 2026-01-27 14:06:37 -07:00
Jeremy Soller e13e24b54e Use annotated tags 2026-01-27 10:30:12 -07:00
Jeremy Soller dafb7bb1fa Add script to automate update of version, currently limited to apps 2026-01-21 10:16:31 -07:00
29 changed files with 87 additions and 32 deletions
+8
View File
@@ -0,0 +1,8 @@
- [ ] I have disclosed use of any AI generated code in my commit messages.
- If you are using an LLM, and do not fully understand the changes it is making to the code base, do not create a PR.
- In our experience, AI generated code often results in overly complex code that lacks enough context for a proper fix or feature inclusion. This results in considerably longer code reviews. Due to this, AI authored or partially authored PRs may be closed without comment.
- [ ] I understand these changes in full and will be able to respond to review comments.
- [ ] My change is accurately described in the commit message.
- [ ] My contribution is tested and working as described.
- [ ] I have read the [Developer Certificate of Origin](https://developercertificate.org/) and certify my contribution under its conditions.
+7 -6
View File
@@ -2,14 +2,15 @@
set -e
TAG="$1"
if [ -z "$TAG" ]
if [ -z "$1" ]
then
echo "$0 [tag]" >&2
echo "$0 [epoch version]" >&2
exit 1
fi
VERSION="$1"
TAG="epoch-$1"
echo "Do you want to tag the current state of cosmic-epoch with the tag $TAG? (y/N)"
read answer
if [ "$answer" != "y" ]
@@ -22,8 +23,8 @@ set -x
git fetch --recurse-submodules
git tag --force "$TAG"
git submodule foreach git tag --force "$TAG"
git tag --force --annotate "$TAG" --message "Epoch ${VERSION}"
git submodule foreach git tag --force --annotate "$TAG" --message "Epoch ${VERSION}"
git push --force origin tag "$TAG"
git submodule foreach git push --force origin tag "$TAG"
+46
View File
@@ -0,0 +1,46 @@
#!/usr/bin/env bash
set -e
# This should be the _next_ epoch version
version=1.0.9
subject="Epoch ${version} version update"
description="Generated by cosmic-epoch scripts/version-update.sh"
repos=(
cosmic-edit
cosmic-files
cosmic-player
cosmic-store
cosmic-term
)
for repo in "${repos[@]}"
do
git submodule update --recursive "${repo}"
pushd "${repo}"
git fetch origin
git checkout -B epoch-update origin/master
git reset --hard
if [ "$(dpkg-parsechangelog --show-field Version)" != "${version}" ]
then
dch --newversion "${version}" --distribution noble "${subject}"
fi
cargo set-version "${version}"
cargo update
git commit -a -m "${subject}" -m "${description}"
git push -f -u origin epoch-update
pr_url="$(gh pr list --head epoch-update --state open --json url --jq '.[].url')"
if [ -n "${pr_url}" ]
then
echo "PR already open: ${pr_url}"
else
gh pr create \
--title "${subject}" \
--body "${description}" \
--assignee "@me" \
--reviewer "pop-os/engineering" \
--reviewer "pop-os/quality-assurance"
fi
popd
done