v0.7

What's Changed

• Fixing the "context deadline exceeded" issue. by @gu-does-git in #46
• Fix the GLIBC errors due to the new OS version used by latest golang docker image by @0x111 in #46

New Contributors

• @gu-does-git made their first contribution in #46

Full Changelog: v0.6...v0.7

v0.6

What's Changed

Servicenow changed the SSO Login again. This release addresses this issue.

• Updated form ids by @robertoalvarezalonso in #43

New Contributors

• @robertoalvarezalonso made their first contribution in #43

Thanks for all the contributions.
Docker images here on github and on docker hub updated to the latest tag too.

Full Changelog: v0.5.3...v0.6

v0.5.3

What's Changed

Servicenow switched to the new SSO recently. This release addresses the new flow and logic.
Also new go version has been used and the go.mod file has been cleaned up.

• Adjust the flow for the new SSO login by @0x111 in #40

Full Changelog: v0.5.2...v0.5.3

v0.5.2

• Fixed an issue with the SSO Login URL #36 (PR #37)

v0.5.1

Fixed issue with the button being not found due to viewport being a mobile view #21

v0.5

• Rewrite the tasks to be run with per action checks, also to have some output on what the app is actually doing
• Add an option to specify timeout in the cli and config file
• Bump go version
• Add the timeout to config.sample.json
• Build the linux version of the app only, this reduces build time
• Add disclaimer and clarify what this app does in the detail to prevent confusions
• Fix #17

v0.5-pre

Pre-release for testing.

Related #18

v0.4

#14 Bump github.com/chromedp/chromedp from 0.3.1 to 0.5.3
#15 Introduced Docker image support.

Servicenow did a redesign of their development portal with the new Orlando release. The app works as the usual further, no changes were needed since the current url works.

Keep sending feedback!

v0.3.1

This is just a minor version update.

• There was a change to the OKTA SSO login page, this prevented the app from working correctly. Fixed by #6
• ChromeDP updated to the latest version in #5 (For more details, see the PR)

v0.3

Introduced a new flag config, this will allow you to dynamically specify the location of your config file.

You can use a relative or absolute path too. For example both of these work -config config.json or -config /home/user/config.json.

Fixed an issue where the flags of the CLI were ignored and there was always a need for a config file #4.

The apps behaviour changed, if you use the -config flag, we will only load the config file and will ignore all of the flags provided if any. Please use -help for more info on the flags and usage.