Skip to content

Releases: lordofscripts/wipechromium

v0.4.0

19 Sep 00:09
Compare
Choose a tag to compare

RELEASE NOTES

Version: v0.4.0

New Features

  • MacOS 64-bit executable (1st appearance) is NOW available.
  • Added Dry Run capability (see -dry CLI flag) which lets you run the application and it will tell you what it would remove/delete without actually changing anything in the underlying OS.
  • Added support for Firefox ESR browser. See -browser firefox CLI flag.

Therefore, wipechromium now supports Chromium & Firefox.

Fixed Problems

None known.

Known Issues

  • Has not been run on Windows or MacOS as I don't have those machines at my disposal.
  • Tested with Firefox ESR on Debian Linux.

Platform-specific

The following are platform-specific notes about the program's functionality,
and/or the Release assets (deliverables).

Linux & Unix

  • Fully operational (Chromium supported). All tests pass. The deliverable is
    not in compressed form and requires chmod ugo+x to be made executable.)
  • Available: Linux 386 & ARM builds

Microsoft Windows

  • Windows build not tested (need feedback on Cache & Profile folders as I
    don't have a Windows machine). Therefore, use at your own risk!. ) It
    uses folders based on the information available on Internet.
  • If downloaded from Release Assets, you must rename the file to EXE with
    rename wipechromium wipechromium.exe
  • Available: Windows 386 build (32-bits)

MacOS

  • MacOS build not tested (need feedback on folders). I don't have a Mac
    machine available to me.
  • Available: Darwin AMD64 (64-bit) build

Change Log

Full Changelog: v0.3.1...v0.4.0

v0.3.1

31 Aug 21:30
Compare
Choose a tag to compare

RELEASE NOTES

Version: v0.3.1

New Features

  • GH-3 The cross-build workflow now correctly produce binaries attached to the release: linux/arm, linux/386 & windows/386.

Fixed Problems

  • GH-5 Compilation on Windows failed due to return values of os.UserCacheDir().

Known Issues

  • May not detect the Cache & Profiles folders correctly on Windows. Please run wipechromium -scan -log and report to me.
  • Forgot to include the MacOS build in the cross-build workflow. AFAIK MacOS/386 is the most-used Mac platform, right?

Platform-specific

The following are platform-specific notes about the program's functionality or the release assets.

Linux & Unix

  • Fully operational (Chromium supported). All tests pass. The deliverable is not in compressed form and requires chmod ugo+x to be made executable.

Microsoft Windows

  • Windows build not tested (need feedback on Cache & Profile folders, I don't have a Windows machine), so use at your own risk!. It uses folders based on the information available on Internet.

MacOS

  • MacOS build not yet provided. It will be made available on the next release. However, I don't have access to a MacOS machine; therefore, I need feedback regarding the actual directories used by Chromium installations on MacOS.

Change Log

Full Changelog: v0.3...v0.3.1

v0.3

28 Aug 22:59
Compare
Choose a tag to compare

WipeChromium v0.3

New Features

  • Added the cleaned size mode (short flag: -z or long flag: -size) to the wipechromium CLI. It defaults to Std but you can specify SI for International System (1KB=1000 bytes) or IEC (1KB=1024 bytes) if you prefer using KB/MB/TB or KiB/MiB/TiB respectively.

Solved Issues

  • GH-2 the program is run, now all messages report sizes in the chosen format (default is Standard, i.e. bytes)

Known Problems

Application: None. The application is working as expected if you build it yourself.
However,
Released Artifacts: only the one marked armv7l is an actual binary. I am still working on GH-3 to solve a problem with the underlying actions of the cross-build workflow which is supposed to produce binary distributables for Windows, MacOS and Intel-based Linux. Have not gotten answers from authors of the cross-build actions.

Change Log

Full Changelog: v0.2.0...v0.3

v0.2.0

28 Aug 01:28
Compare
Choose a tag to compare

Change Log

Full Changelog: v0.1.0...v0.2.0

New Features

  • Size reporting now reports the actual savings in (Mega) bytes. Previously it was not counting directories well.
  • Introduced Virtual File System support (internally)
  • Cross-build seems to be working

Other Issues

  • New test cases to improve test coverage
  • Reformatting for Go Report Card although that site lags behind 3+ days

Known Problems

  • GitHub problem generating cross-build binaries again

Initial Release v0.1

27 Aug 12:14
Compare
Choose a tag to compare

The Chromium Wiper saves a lot of space occupied by junk. It works at user-profile level as every user account can use the Chromium-based browsers in one of many user profiles. Many users just stick to Default but many choose to partition their browsing into meaningful profiles.