alessandro-marcantoni / scala-types

Providing scala types implementation for typescript

Hi there! 👋 I'm Alessandro

🤓 About Me

• Master's graduate in Computer Science and Engineering from the University of Bologna
• Cloud Engineer @ Connect Reply, specializing in AWS - Java - Spring
• Freelancing for a startup, leading a full-stack project with Kotlin - Ktor - Typescript - React

🤔 Interests

• Exploring large-scale IoT systems' solutions and their impact on modern technology
• Delving into the intricacies of functional programming paradigms
• Experimenting with simulations to model complex real-world scenarios
• Eager to learn more about the fascinating field of data engineering

🧰 Languages and Tools

🖖 Get In Touch

• LinkedIn: Alessandro Marcantoni
• Email: [email protected]

Feel free to reach out if you share similar interests or want to collaborate on exciting projects!

📈 Some of my Github Stats

scala-types's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	tslint

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency eslint to v8.57.0
• chore(deps): update codecov/codecov-action action to v4
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency husky to v9
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency husky to v8.0.3
• chore(deps): update dependency ts-node to v10.9.2
• chore(deps): update dependency ts-jest to v29.1.5
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update jest monorepo (@types/jest, jest)
• chore(deps): update typescript-eslint monorepo to v5.62.0 (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency typescript to v5
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/cd.yaml

• actions/checkout v3
• actions/setup-node v3

.github/workflows/ci.yaml

• actions/checkout v3
• actions/setup-node v3
• codecov/codecov-action v3

npm

package.json

• @types/jest 29.0.3
• @typescript-eslint/eslint-plugin 5.32.0
• @typescript-eslint/parser 5.32.0
• eslint 8.21.0
• eslint-config-google 0.14.0
• husky 8.0.1
• jest 29.0.3
• ts-jest 29.0.1
• ts-node 10.9.1
• tslint 6.1.3
• typescript 4.8.3

---

• Check this box to trigger a request for Renovate to run again on this repository

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://x-access-token:[secure]@github.com/alessandro-marcantoni/scala-types.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀