Release 0.9.78 discussion

[kmk3]

Release links:

• Project board: (None)
• GitHub Release: https://github.com/netblue30/firejail/releases/tag/0.9.78

Discussion for the previous release:

• Release 0.9.76 discussion #6691

Discussion for the next release:

• Release 0.9.80 discussion #7016

Discussions for this release:

• Create a GitHub Project for 0.9.78 #6835
• build: 0.9.78: release tag is in the wrong commit (version 0.9.79) #7025

Release checklist:

• Add a link above for the discussion of the previous release
• Create a GitHub Project for this release and link it above
• Bump the current version to release in configure.ac/configure
• Update the release version and date in the RELNOTES
• Complete RELNOTES
• Complete README
• Create an annotated git tag and push it (git tag -s or git tag -a)
• Create a new GitHub Release and link it above

Post-release checklist:

• Update the supported versions in SECURITY.md
• Update the supported versions in the issue templates
• Bump the current version to development in configure.ac/configure
• Add a new WIP release in the RELNOTES
• Update the released/current versions in README.md
• Create a discussion for the next release and link it above
• Close this discussion

[netblue30]

New release coming in early January: profiles, new features, and bugfixes. The biggest issue is #6906. It affects Fedora and partially Arch Linux.

[lucasmz-dev]

Firefox will start using .config/mozilla or .config/firefox (unsure?) in 147. I suppose a lot of people use firejail with firefox, and it should be able to do deal with that: https://www.phoronix.com/news/Firefox-147-XDG-Base-Directory

[rusty-snake]

+// UNIX   : ~/.mozilla/ or ${XDG_CONFIG_HOME:-~/.config}/mozilla
+//          if env var MOZ_LEGACY_HOME is set to 1, then ~/.mozilla/ is used

[rusty-snake]

I do not see migration code. Maybe is only affects new installations. For the most packaged firefoxes (apt, dnf, ...) the distribution specific wrappers needs to be updated to because the place files in .mozilla before the real Firefox starts.

[kmk3]

Firefox will start using .config/mozilla or .config/firefox (unsure?) in 147.
I suppose a lot of people use firejail with firefox, and it should be able to
do deal with that:
https://www.phoronix.com/news/Firefox-147-XDG-Base-Directory

Good catch.

Really unfortunate decision to follow the mistakes of Chromium (and
derivatives) and put megabytes/gigabytes of data into ~/.config instead of
~/.local/share where it belongs (that is, if you are going to dump all
config/data into one directory anyway as currently is the case).

It makes no sense as per the standard and IMO just makes everything worse
compared to just leaving it at ~/.mozilla.

Hopefully it can be fixed.

Either way, if a new directory is confirmed/released, please submit a PR.

I can organize a 0.9.78.1 and backport the PR later if needed.

[lucasmz-dev]

I believe it is only applicable for new profiles and there's no migration code yet, that's my understanding

Unclear to me how to trigger it, and it's in 147 so I'd have to test a Nightly build I guess.

[kmk3]

Fixed in:

• profiles: firefox: add new ~/.config/mozilla dir #7061

[kmk3]

@netblue30

The 0.9.78 git tag is currently a lightweight tag, which is ignored for some
git operations.

Can you replace it with an annotated tag?

Example:

# Delete local lightweight tag
git tag -d 0.9.78

# Create new annotated tag
git tag -a 0.9.78

# Delete remote lightweight tag
git push origin --delete 0.9.78

# Push new annotated tag
git push origin 0.9.78

Related:

• Release 0.9.76 discussion #6691 (comment)

[kmk3]

@netblue30

The original git tag command was missing the target commit, so it created the
tag on whatever was the HEAD commit.

Original commit for the tag:

• 196de37

Current commit for the tag:

• 35d6100

Changes:

• 196de37...35d6100

The differences from the tarball should only be in the README/RELNOTES and the
program version (0.9.79), so no functional changes.

Fix

The following should fix it by creating the tag on the correct commit and with
the date being the same as on RELNOTES:

# Delete local tag
git tag -d 0.9.78

# Create new annotated tag
GIT_COMMITTER_DATE='2026-01-03 11:00:00 -0500' git tag -a 0.9.78 196de37df4f98061341476f8fa9f84b369d06a7a

# Delete remote tag
git push origin --delete 0.9.78

# Push new tag
git push origin 0.9.78

Relates to:

• build: 0.9.78: release tag is in the wrong commit (version 0.9.79) #7025

[netblue30]

all set!

[csswright]

Is there anything preventing a release of 0.9.78?

[netblue30]

@csswright , I have no idea what is going on! It was released about two weeks ago.

[netblue30]

Thanks @csswright !

Maybe it is because I re-pushed the tag. The tag created automatically by github.com release page apparently is a lightweight tag, I keep forgetting that (see the message from @kmk3 above).

[kmk3]

@netblue30

Hello, while the GitHub Release was fixed, the release tag is still in the
wrong commit (see #7025).

Can you try the fix in this comment?

• Release 0.9.78 discussion #6841 (reply in thread)

Then it might be necessary to re-enable the GitHub Release again.