Latest builds failing with RegEx parsing issue

[dend]

See example job on OpenSearch:

Pattern syntax error near position 0: recursive wildcards must form a single path component

I've noticed the same problem on my own blog (private repository). Any thoughts on what might be causing it?

The job I am running is mapped to the following YAML file:

name: Link Checker

on:
  repository_dispatch:
  workflow_dispatch:
  schedule:
    - cron: "00 18 * * *"

jobs:
  linkChecker:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2

      - name: Load Excludes
        run: |
          LYCHEE_EXCLUDE=$(sed -e :a  -e 'N;s/\n/ /;ta' .lycheeexclude)
          echo "LYCHEE_EXCLUDE=$LYCHEE_EXCLUDE" >> $GITHUB_ENV

      - name: Link Checker
        uses: lycheeverse/lychee-action@master
        with:
          args: --accept=200,429 --exclude ${{ env.LYCHEE_EXCLUDE }} --exclude-mail "**/*.md"
        env:
          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
        
      - name: Create Issue From File
        uses: peter-evans/create-issue-from-file@v3
        with:
          title: Link Checker Report
          content-filepath: ./lychee/out.md
          labels: report, automated issue

[dend]

So, as it turns out - something changes and the globs need not be wrapped in quotes. Not sure if this was documented/changed somewhere.

[vipulgupta2048]

Hey @dend I never had quotes on my globs but the parsing issue is still there. I don't see any errors on my run like you do. https://github.com/lycheeverse/lychee/issues/436

[dend]

@vipulgupta2048 this worked in previous releases, and even affected OpenSearch, as linked below. Not saying that using quotation marks was the right approach, however something definitely changed in latest releases that resulted in using those breaking jobs 😄

[mre]

This should be fixed in master now. Can you check again @dend or @vipulgupta2048?

[vipulgupta2048]

The master version work. Looking forward to the release soon: #68 (comment)