Artifact not created since switching to v13 of gitlab runner

Hi!
Since we switched to the v13 of the gitlab runner, our CI pipeline is not producing the artifact files as it is suppose to do on our build job… Do you have an idea where the problem can be?

Our yaml file is very simple for the build job:

image: node:10
build:
  stage: build
  cache:
    key: ${CI_COMMIT_REF_SLUG}
    paths:
      - node_modules/
  script:
  - npm install --unsafe-perm
  - npm run tsc
  artifacts:
    paths:
      - .
    expire_in: 1 week

Here are the logs for the build phase, last week (running on the v12)

Running with gitlab-runner 12.10.0-rc2 (6c8c540f)
   on docker-auto-scale 0277ea0f
Preparing the "docker+machine" executor
00:47
 Using Docker executor with image node:10 ...
 Starting service postgres:11 ...
 Pulling docker image postgres:11 ...
 Using docker image sha256:028e3a6bd9eb8ea6335f3f8603329929d2e8978867e4093cd246c3b5cf92f0dd for postgres:11 ...
 Waiting for services to be up and running...
 Pulling docker image node:10 ...
 Using docker image sha256:a02c9f46f94a6e2d03da7973d9f820f4158a3243711d74309a7482b61f3e755f for node:10 ...
Preparing environment
00:05
 Running on runner-0277ea0f-project-5503250-concurrent-0 via runner-0277ea0f-srm-1589373904-1b2818cc...
Getting source from Git repository
00:04
 $ eval "$CI_PRE_CLONE_SCRIPT"
 Fetching changes...
 Initialized empty Git repository in /builds/optimetriks/spabackend/service-web-api/.git/
 Created fresh repository.
 From https://gitlab.com/optimetriks/spabackend/service-web-api
 [...]
 Checking out f7c35d15 as develop...
 Skipping Git submodules setup
Restoring cache
00:13
 Checking cache for develop-9...
 Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/5503250/develop-9 
 Successfully extracted cache
Downloading artifacts
00:01
Running before_script and script
00:22
 $ echo "running build for $CI_PROJECT_NAME"
 running build for service-web-api
 $ npm install --unsafe-perm
 npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
 npm notice created a lockfile as package-lock.json. You should commit this file.
 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.3 (node_modules/sane/node_modules/fsevents):
 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/cpx/node_modules/chokidar/node_modules/fsevents):
 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
 npm WARN enoent ENOENT: no such file or directory, open '/builds/optimetriks/spabackend/service-web-api/node_modules/cpx/node_modules/fsevents/package.json'
 npm WARN enoent ENOENT: no such file or directory, open '/builds/optimetriks/spabackend/service-web-api/node_modules/cpx/node_modules/fsevents/node_modules/rc/package.json'
 npm WARN ts-jest@22.4.6 requires a peer of typescript@2.x but none is installed. You must install peer dependencies yourself.
 audited 1666 packages in 8.466s
 19 packages are looking for funding
   run `npm fund` for details
 found 188 vulnerabilities (170 low, 18 moderate)
   run `npm audit fix` to fix them, or `npm audit` for details
 $ npm run tsc
 > service-web-api@1.0.0 tsc /builds/optimetriks/spabackend/service-web-api
 > tsc --noEmitOnError false
Running after_script
00:01
 Running after script...
 $ echo "stage complete"
 stage complete
Saving cache
00:18
 Creating cache develop-9...
 node_modules/: found 39076 matching files          
 Uploading cache.zip to https://storage.googleapis.com/gitlab-com-runners-cache/project/5503250/develop-9 
 Created cache
Uploading artifacts for successful job
00:22
 Uploading artifacts...
 .: found 39887 matching files                      
 WARNING: Part of .git directory is on the list of files to archive 
 WARNING: This may introduce unexpected problems    
 Uploading artifacts to coordinator... ok            id=550466977 responseStatus=201 Created token=66GgN-mC
 Job succeeded

Here are the logs for the same pipeline, but ran today (with the v13)

Running with gitlab-runner 13.0.0-rc1 (f319718d)
   on docker-auto-scale ed2dce3a
Preparing the "docker+machine" executor
00:56
 Using Docker executor with image node:10 ...
 Starting service postgres:11 ...
 Pulling docker image postgres:11 ...
 Using docker image sha256:01800ccff5d2afe821d3e1d57fccd511798a6371c11d4969dd2e4e4c9f9c7541 for postgres:11 ...
 Waiting for services to be up and running...
 Pulling docker image node:10 ...
 Using docker image sha256:c5f1efe092a05c95b1da2b897fe13ec824990483c7e80766405409989dcc21e7 for node:10 ...
Preparing environment
00:06
 Running on runner-ed2dce3a-project-5503250-concurrent-0 via runner-ed2dce3a-srm-1589720563-297e0d64...
Getting source from Git repository
00:03
 $ eval "$CI_PRE_CLONE_SCRIPT"
 Fetching changes...
 Initialized empty Git repository in /builds/optimetriks/spabackend/service-web-api/.git/
 Created fresh repository.
 From https://gitlab.com/optimetriks/spabackend/service-web-api
  [...]
 Checking out f7c35d15 as develop...
 Skipping Git submodules setup
Restoring cache
00:12
 Checking cache for develop-9...
 Downloading cache.zip from https://storage.googleapis.com/gitlab-com-runners-cache/project/5503250/develop-9 
 Successfully extracted cache
Downloading artifacts
00:02
Running before_script and script
00:31
 $ echo "running build for $CI_PROJECT_NAME"
 running build for service-web-api
 $ npm install --unsafe-perm
 npm WARN deprecated joi@14.3.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
 npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
 npm notice created a lockfile as package-lock.json. You should commit this file.
 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.3 (node_modules/sane/node_modules/fsevents):
 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/cpx/node_modules/chokidar/node_modules/fsevents):
 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
 npm WARN enoent ENOENT: no such file or directory, open '/builds/optimetriks/spabackend/service-web-api/node_modules/cpx/node_modules/fsevents/package.json'
 npm WARN enoent ENOENT: no such file or directory, open '/builds/optimetriks/spabackend/service-web-api/node_modules/cpx/node_modules/fsevents/node_modules/rc/package.json'
 npm WARN ts-jest@22.4.6 requires a peer of typescript@2.x but none is installed. You must install peer dependencies yourself.
 updated 2 packages and audited 1666 packages in 18.107s
 18 packages are looking for funding
   run `npm fund` for details
 found 188 vulnerabilities (170 low, 18 moderate)
   run `npm audit fix` to fix them, or `npm audit` for details
 $ npm run tsc
 > service-web-api@1.0.0 tsc /builds/optimetriks/spabackend/service-web-api
 > tsc --noEmitOnError false
Running after_script
00:02
 Running after script...
 $ echo "stage complete"
 stage complete
Saving cache
00:19
 Creating cache develop-9...
 node_modules/: found 39069 matching files          
 Uploading cache.zip to https://storage.googleapis.com/gitlab-com-runners-cache/project/5503250/develop-9 
 Created cache
Uploading artifacts for successful job
00:01
 Uploading artifacts...
 WARNING: .: no matching files                      
 ERROR: No files to upload                          
 Job succeeded

Thank you in advance for your help! :pray:

We solved the problem by adding a slash / character to the artifacts path (./ instead of .)