Added more details about go1.24 issue and debug (#159)

* Added more details about go1.24 issue and debug

* correct check

Add progress bar/spinner (on by default) (#158)

* Add progress bar/spinner (on by default)

* Temp test with 1.24.1 to check if the issue shows up on CI too

* Add note about macos issue, get back to 1.23 build and 1.20 go.mod requirement

Deal with os matrix / absence of docker. Update dependencies but avoi…

…d x/tools 0.25.0 which forces go 1.22 upgrade (#155)

* Deal with os matrix / absence of docker. Update dependencies but avoid x/tools 0.25.0 which forces go 1.22 upgrade

* avoid issue with wrong openssl in the macos github action

* switching strategy re docker

* windows error is different

* seems txtar/testscript files don't work on windows

* more windows error message difference

* Pass token down for codecov

* last 2 windows error adjustments, hopefully

* giving up on tescript on windows because of the -- issue

Bump fortio.org/cli from 1.6.0 to 1.7.0 (#148)

Bumps [fortio.org/cli](https://github.com/fortio/cli) from 1.6.0 to 1.7.0.
- [Release notes](https://github.com/fortio/cli/releases)
- [Commits](fortio/cli@v1.6.0...v1.7.0)

---
updated-dependencies:
- dependency-name: fortio.org/cli
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Simplify from scratch docker - use built in go CA bundle (#146)

Note: the commit steps in the original MR is worth checking

* adding local docker test - before addressing #145

* remove alpine

test/connect will fail with 16:07:44 [E] 1: Error fetching 18.222.136.83: Get "https://debug.fortio.org/build-test": tls: failed to verify certificate: x509: certificate signed by unknown authority

* use fortio/workflows#47 to show failure of image in current state

* don't check goreleaser in go checks

* meant to not add all the files before but... lets fix the linter first

* Making CI fail again until we bump cli package

* pre test the cli release, also add negative test

* get the non pre release

* Move bundle mention to Dockerfile

Bump fortio.org/log from 1.12.1 to 1.12.2 (#144)

Bumps [fortio.org/log](https://github.com/fortio/log) from 1.12.1 to 1.12.2.
- [Release notes](https://github.com/fortio/log/releases)
- [Commits](fortio/log@v1.12.1...v1.12.2)

---
updated-dependencies:
- dependency-name: fortio.org/log
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Use shared workflows and linter/releaser configs (#139)

* first attempt at shared workflows

* fix up path

* ignore downloaded file so goreleaser hopefully doesn't complain

* delete the original .goreleaser.yaml

* add gochecks

* .golangci.yml is now downloaded from workflows/

* fix lints

Empty commit to retrigger actions - #4

Catch up to latest 'final' log output [LVL] (#94)

* Catch up to latest 'final' log output [LVL]

* update the tests

Bump fortio.org/cli from 1.1.0 to 1.2.0 (#83)

Bumps [fortio.org/cli](https://github.com/fortio/cli) from 1.1.0 to 1.2.0.
- [Release notes](https://github.com/fortio/cli/releases)
- [Commits](fortio/cli@v1.1.0...v1.2.0)

---
updated-dependencies:
- dependency-name: fortio.org/cli
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>